Beam Failure Management for Preconfigured Resource

ABSTRACT

A wireless device receives a release message indicating a small data transmission (SDT) procedure, of a cell, for an inactive state of the wireless device and indicating a downlink reference signal (RS), of a plurality of downlink RSs of the cell, associated with the SDT procedure. The wireless device initiates, during the SDT procedure, a beam failure detection and recovery procedure on the cell based on a measurement quantity of the downlink RS compared with a first threshold, and based on a cell measurement quantity, of one or more downlink RSs of the plurality downlink RSs, compared with a second threshold.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.17/396,136, filed Aug. 6, 2021, which claims the benefit of U.S.Provisional Application No. 63/062,412, filed Aug. 6, 2020, all of whichare hereby incorporated by reference in their entireties.

BRIEF DESCRIPTION OF THE DRAWINGS

Examples of several of the various embodiments of the present disclosureare described herein with reference to the drawings.

FIG. 1A and FIG. 1B illustrate example mobile communication networks inwhich embodiments of the present disclosure may be implemented.

FIG. 2A and FIG. 2B respectively illustrate a New Radio (NR) user planeand control plane protocol stack.

FIG. 3 illustrates an example of services provided between protocollayers of the NR user plane protocol stack of FIG. 2A.

FIG. 4A illustrates an example downlink data flow through the NR userplane protocol stack of FIG. 2A.

FIG. 4B illustrates an example format of a MAC subheader in a MAC PDU.

FIG. 5A and FIG. 5B respectively illustrate a mapping between logicalchannels, transport channels, and physical channels for the downlink anduplink.

FIG. 6 is an example diagram showing RRC state transitions of a UE.

FIG. 7 illustrates an example configuration of an NR frame into whichOFDM symbols are grouped.

FIG. 8 illustrates an example configuration of a slot in the time andfrequency domain for an NR carrier.

FIG. 9 illustrates an example of bandwidth adaptation using threeconfigured BWPs for an NR carrier.

FIG. 10A illustrates three carrier aggregation configurations with twocomponent carriers.

FIG. 10B illustrates an example of how aggregated cells may beconfigured into one or more PUCCH groups.

FIG. 11A illustrates an example of an SS/PBCH block structure andlocation.

FIG. 11B illustrates an example of CSI-RSs that are mapped in the timeand frequency domains.

FIG. 12A and FIG. 12B respectively illustrate examples of three downlinkand uplink beam management procedures.

FIG. 13A, FIG. 13B, and FIG. 13C respectively illustrate a four-stepcontention-based random access procedure, a two-step contention-freerandom access procedure, and another two-step random access procedure.

FIG. 14A illustrates an example of CORESET configurations for abandwidth part.

FIG. 14B illustrates an example of a CCE-to-REG mapping for DCItransmission on a CORESET and PDCCH processing.

FIG. 15 illustrates an example of a wireless device in communicationwith a base station.

FIG. 16A, FIG. 16B, FIG. 16C, and FIG. 16D illustrate example structuresfor uplink and downlink transmission.

FIG. 17 illustrates an example of one or more data packettransmission(s) in an RRC_INACTIVE state (or an RRC_IDLE state),according to some embodiments.

FIG. 18A illustrates an example of (pre-)configured grant(s) indicatingone or more uplink radio resources in a Non-RRC_CONNECTED (e.g.,RRC_INACTIVE state and/or an RRC_IDLE state), according to someembodiments.

FIG. 18B illustrates an example of (pre-)configured grant(s) indicatingone or more uplink radio resources in a Non-RRC_CONNECTED (e.g.,RRC_INACTIVE state and/or an RRC_IDLE state), according to someembodiments.

FIG. 19 illustrates an example of one or more data packettransmission(s) in a Non-RRC_CONNECTED (e.g., RRC_INACTIVE and/or anRRC_IDLE) state, according to some embodiments.

FIG. 20 illustrates an example of one or more data packettransmission(s) in a Non-RRC_CONNECTED (e.g., RRC_INACTIVE and/or anRRC_IDLE) state, according to some embodiments.

FIG. 21A illustrates an example of TA validation, according to someembodiments.

FIG. 21B illustrates an example of TA validation, according to someembodiments.

FIG. 22 illustrates an example geographical view of an increasethreshold value and/or a decrease threshold value, according to someembodiments.

FIG. 23 illustrates an example of one or more radio resource(s) in a BWP(e.g., DL BWP and/or UL BWP), according to some embodiments.

FIG. 24 illustrates an example of beam management for transmissionand/or reception in a Non-RRC_CONNECTED state, according to someembodiments.

FIG. 25 illustrates an example of a beam failure detection and/orrecovery procedure, according to some embodiments.

FIG. 26 illustrates an example of a cell (re-)selection procedure,according to some embodiments.

FIG. 27 illustrates an example of a cell (re-)selection procedure and/orbeam failure detection/recovery procedure, according to someembodiments.

FIG. 28 illustrates an example of beam failure detection and/or recoveryprocedure, according to some embodiments.

FIG. 29 illustrates an example of a cell (re-)selection procedure,according to some embodiments.

DETAILED DESCRIPTION

In the present disclosure, various embodiments are presented as examplesof how the disclosed techniques may be implemented and/or how thedisclosed techniques may be practiced in environments and scenarios. Itwill be apparent to persons skilled in the relevant art that variouschanges in form and detail can be made therein without departing fromthe scope. In fact, after reading the description, it will be apparentto one skilled in the relevant art how to implement alternativeembodiments. The present embodiments should not be limited by any of thedescribed exemplary embodiments. The embodiments of the presentdisclosure will be described with reference to the accompanyingdrawings. Limitations, features, and/or elements from the disclosedexample embodiments may be combined to create further embodiments withinthe scope of the disclosure. Any figures which highlight thefunctionality and advantages, are presented for example purposes only.The disclosed architecture is sufficiently flexible and configurable,such that it may be utilized in ways other than that shown. For example,the actions listed in any flowchart may be re-ordered or only optionallyused in some embodiments.

Embodiments may be configured to operate as needed. The disclosedmechanism may be performed when certain criteria are met, for example,in a wireless device, a base station, a radio environment, a network, acombination of the above, and/or the like. Example criteria may bebased, at least in part, on for example, wireless device or network nodeconfigurations, traffic load, initial system set up, packet sizes,traffic characteristics, a combination of the above, and/or the like.When the one or more criteria are met, various example embodiments maybe applied. Therefore, it may be possible to implement exampleembodiments that selectively implement disclosed protocols.

A base station may communicate with a mix of wireless devices. Wirelessdevices and/or base stations may support multiple technologies, and/ormultiple releases of the same technology. Wireless devices may have somespecific capability(ies) depending on wireless device category and/orcapability(ies). When this disclosure refers to a base stationcommunicating with a plurality of wireless devices, this disclosure mayrefer to a subset of the total wireless devices in a coverage area. Thisdisclosure may refer to, for example, a plurality of wireless devices ofa given LTE or 5G release with a given capability and in a given sectorof the base station. The plurality of wireless devices in thisdisclosure may refer to a selected plurality of wireless devices, and/ora subset of total wireless devices in a coverage area which performaccording to disclosed methods, and/or the like. There may be aplurality of base stations or a plurality of wireless devices in acoverage area that may not comply with the disclosed methods, forexample, those wireless devices or base stations may perform based onolder releases of LTE or 5G technology.

In this disclosure, “a” and “an” and similar phrases are to beinterpreted as “at least one” and “one or more.” Similarly, any termthat ends with the suffix “(s)” is to be interpreted as “at least one”and “one or more.” In this disclosure, the term “may” is to beinterpreted as “may, for example.” In other words, the term “may” isindicative that the phrase following the term “may” is an example of oneof a multitude of suitable possibilities that may, or may not, beemployed by one or more of the various embodiments. The terms“comprises” and “consists of”, as used herein, enumerate one or morecomponents of the element being described. The term “comprises” isinterchangeable with “includes” and does not exclude unenumeratedcomponents from being included in the element being described. Bycontrast, “consists of” provides a complete enumeration of the one ormore components of the element being described. The term “based on”, asused herein, should be interpreted as “based at least in part on” ratherthan, for example, “based solely on”. The term “and/or” as used hereinrepresents any possible combination of enumerated elements. For example,“A, B, and/or C” may represent A; B; C; A and B; A and C; B and C; or A,B, and C.

If A and B are sets and every element of A is an element of B, A iscalled a subset of B. In this specification, only non-empty sets andsubsets are considered. For example, possible subsets of B={cell1,cell2} are: {cell1}, {cell2}, and {cell1, cell2}. The phrase “based on”(or equally “based at least on”) is indicative that the phrase followingthe term “based on” is an example of one of a multitude of suitablepossibilities that may, or may not, be employed to one or more of thevarious embodiments. The phrase “in response to” (or equally “inresponse at least to”) is indicative that the phrase following thephrase “in response to” is an example of one of a multitude of suitablepossibilities that may, or may not, be employed to one or more of thevarious embodiments. The phrase “depending on” (or equally “depending atleast to”) is indicative that the phrase following the phrase “dependingon” is an example of one of a multitude of suitable possibilities thatmay, or may not, be employed to one or more of the various embodiments.The phrase “employing/using” (or equally “employing/using at least”) isindicative that the phrase following the phrase “employing/using” is anexample of one of a multitude of suitable possibilities that may, or maynot, be employed to one or more of the various embodiments.

The term configured may relate to the capacity of a device whether thedevice is in an operational or non-operational state. Configured mayrefer to specific settings in a device that effect the operationalcharacteristics of the device whether the device is in an operational ornon-operational state. In other words, the hardware, software, firmware,registers, memory values, and/or the like may be “configured” within adevice, whether the device is in an operational or nonoperational state,to provide the device with specific characteristics. Terms such as “acontrol message to cause in a device” may mean that a control messagehas parameters that may be used to configure specific characteristics ormay be used to implement certain actions in the device, whether thedevice is in an operational or non-operational state.

In this disclosure, parameters (or equally called, fields, orInformation elements: IEs) may comprise one or more information objects,and an information object may comprise one or more other objects. Forexample, if parameter (IE) N comprises parameter (IE) M, and parameter(IE) M comprises parameter (IE) K, and parameter (IE) K comprisesparameter (information element) J. Then, for example, N comprises K, andN comprises J. In an example embodiment, when one or more messagescomprise a plurality of parameters, it implies that a parameter in theplurality of parameters is in at least one of the one or more messages,but does not have to be in each of the one or more messages.

Many features presented are described as being optional through the useof “may” or the use of parentheses. For the sake of brevity andlegibility, the present disclosure does not explicitly recite each andevery permutation that may be obtained by choosing from the set ofoptional features. The present disclosure is to be interpreted asexplicitly disclosing all such permutations. For example, a systemdescribed as having three optional features may be embodied in sevenways, namely with just one of the three possible features, with any twoof the three possible features or with three of the three possiblefeatures.

Many of the elements described in the disclosed embodiments may beimplemented as modules. A module is defined here as an element thatperforms a defined function and has a defined interface to otherelements. The modules described in this disclosure may be implemented inhardware, software in combination with hardware, firmware, wetware (e.g.hardware with a biological element) or a combination thereof, which maybe behaviorally equivalent. For example, modules may be implemented as asoftware routine written in a computer language configured to beexecuted by a hardware machine (such as C, C++, Fortran, Java, Basic,Matlab or the like) or a modeling/simulation program such as Simulink,Stateflow, GNU Octave, or Lab VIEWMathScript. It may be possible toimplement modules using physical hardware that incorporates discrete orprogrammable analog, digital and/or quantum hardware. Examples ofprogrammable hardware comprise: computers, microcontrollers,microprocessors, application-specific integrated circuits (ASICs); fieldprogrammable gate arrays (FPGAs); and complex programmable logic devices(CPLDs). Computers, microcontrollers and microprocessors are programmedusing languages such as assembly, C, C++ or the like. FPGAs, ASICs andCPLDs are often programmed using hardware description languages (HDL)such as VHSIC hardware description language (VHDL) or Verilog thatconfigure connections between internal hardware modules with lesserfunctionality on a programmable device. The mentioned technologies areoften used in combination to achieve the result of a functional module.

FIG. 1A illustrates an example of a mobile communication network 100 inwhich embodiments of the present disclosure may be implemented. Themobile communication network 100 may be, for example, a public landmobile network (PLMN) run by a network operator. As illustrated in FIG.1A, the mobile communication network 100 includes a core network (CN)102, a radio access network (RAN) 104, and a wireless device 106.

The CN 102 may provide the wireless device 106 with an interface to oneor more data networks (DNs), such as public DNs (e.g., the Internet),private DNs, and/or intra-operator DNs. As part of the interfacefunctionality, the CN 102 may set up end-to-end connections between thewireless device 106 and the one or more DNs, authenticate the wirelessdevice 106, and provide charging functionality.

The RAN 104 may connect the CN 102 to the wireless device 106 throughradio communications over an air interface. As part of the radiocommunications, the RAN 104 may provide scheduling, radio resourcemanagement, and retransmission protocols. The communication directionfrom the RAN 104 to the wireless device 106 over the air interface isknown as the downlink and the communication direction from the wirelessdevice 106 to the RAN 104 over the air interface is known as the uplink.Downlink transmissions may be separated from uplink transmissions usingfrequency division duplexing (FDD), time-division duplexing (TDD),and/or some combination of the two duplexing techniques.

The term wireless device may be used throughout this disclosure to referto and encompass any mobile device or fixed (non-mobile) device forwhich wireless communication is needed or usable. For example, awireless device may be a telephone, smart phone, tablet, computer,laptop, sensor, meter, wearable device, Internet of Things (IoT) device,vehicle road side unit (RSU), relay node, automobile, and/or anycombination thereof. The term wireless device encompasses otherterminology, including user equipment (UE), user terminal (UT), accessterminal (AT), mobile station, handset, wireless transmit and receiveunit (WTRU), and/or wireless communication device.

The RAN 104 may include one or more base stations (not shown). The termbase station may be used throughout this disclosure to refer to andencompass a Node B (associated with UMTS and/or 3G standards), anEvolved Node B (eNB, associated with E-UTRA and/or 4G standards), aremote radio head (RRH), a baseband processing unit coupled to one ormore RRHs, a repeater node or relay node used to extend the coveragearea of a donor node, a Next Generation Evolved Node B (ng-eNB), aGeneration Node B (gNB, associated with NR and/or 5G standards), anaccess point (AP, associated with, for example, WiFi or any othersuitable wireless communication standard), and/or any combinationthereof. A base station may comprise at least one gNB Central Unit(gNB-CU) and at least one a gNB Distributed Unit (gNB-DU).

A base station included in the RAN 104 may include one or more sets ofantennas for communicating with the wireless device 106 over the airinterface. For example, one or more of the base stations may includethree sets of antennas to respectively control three cells (or sectors).The size of a cell may be determined by a range at which a receiver(e.g., a base station receiver) can successfully receive thetransmissions from a transmitter (e.g., a wireless device transmitter)operating in the cell. Together, the cells of the base stations mayprovide radio coverage to the wireless device 106 over a wide geographicarea to support wireless device mobility.

In addition to three-sector sites, other implementations of basestations are possible. For example, one or more of the base stations inthe RAN 104 may be implemented as a sectored site with more or less thanthree sectors. One or more of the base stations in the RAN 104 may beimplemented as an access point, as a baseband processing unit coupled toseveral remote radio heads (RRHs), and/or as a repeater or relay nodeused to extend the coverage area of a donor node. A baseband processingunit coupled to RRHs may be part of a centralized or cloud RANarchitecture, where the baseband processing unit may be eithercentralized in a pool of baseband processing units or virtualized. Arepeater node may amplify and rebroadcast a radio signal received from adonor node. A relay node may perform the same/similar functions as arepeater node but may decode the radio signal received from the donornode to remove noise before amplifying and rebroadcasting the radiosignal.

The RAN 104 may be deployed as a homogenous network of macrocell basestations that have similar antenna patterns and similar high-leveltransmit powers. The RAN 104 may be deployed as a heterogeneous network.In heterogeneous networks, small cell base stations may be used toprovide small coverage areas, for example, coverage areas that overlapwith the comparatively larger coverage areas provided by macrocell basestations. The small coverage areas may be provided in areas with highdata traffic (or so-called “hotspots”) or in areas with weak macrocellcoverage. Examples of small cell base stations include, in order ofdecreasing coverage area, microcell base stations, picocell basestations, and femtocell base stations or home base stations.

The Third-Generation Partnership Project (3GPP) was formed in 1998 toprovide global standardization of specifications for mobilecommunication networks similar to the mobile communication network 100in FIG. 1A. To date, 3GPP has produced specifications for threegenerations of mobile networks: a third generation (3G) network known asUniversal Mobile Telecommunications System (UMTS), a fourth generation(4G) network known as Long-Term Evolution (LTE), and a fifth generation(5G) network known as 5G System (5GS). Embodiments of the presentdisclosure are described with reference to the RAN of a 3GPP 5G network,referred to as next-generation RAN (NG-RAN). Embodiments may beapplicable to RANs of other mobile communication networks, such as theRAN 104 in FIG. 1A, the RANs of earlier 3G and 4G networks, and those offuture networks yet to be specified (e.g., a 3GPP 6G network). NG-RANimplements 5G radio access technology known as New Radio (NR) and may beprovisioned to implement 4G radio access technology or other radioaccess technologies, including non-3GPP radio access technologies.

FIG. 1B illustrates another example mobile communication network 150 inwhich embodiments of the present disclosure may be implemented. Mobilecommunication network 150 may be, for example, a PLMN run by a networkoperator. As illustrated in FIG. 1B, mobile communication network 150includes a 5G core network (5G-CN) 152, an NG-RAN 154, and UEs 156A and156B (collectively UEs 156). These components may be implemented andoperate in the same or similar manner as corresponding componentsdescribed with respect to FIG. 1A.

The 5G-CN 152 provides the UEs 156 with an interface to one or more DNs,such as public DNs (e.g., the Internet), private DNs, and/orintra-operator DNs. As part of the interface functionality, the 5G-CN152 may set up end-to-end connections between the UEs 156 and the one ormore DNs, authenticate the UEs 156, and provide charging functionality.Compared to the CN of a 3GPP 4G network, the basis of the 5G-CN 152 maybe a service-based architecture. This means that the architecture of thenodes making up the 5G-CN 152 may be defined as network functions thatoffer services via interfaces to other network functions. The networkfunctions of the 5G-CN 152 may be implemented in several ways, includingas network elements on dedicated or shared hardware, as softwareinstances running on dedicated or shared hardware, or as virtualizedfunctions instantiated on a platform (e.g., a cloud-based platform).

As illustrated in FIG. 1B, the 5G-CN 152 includes an Access and MobilityManagement Function (AMF) 158A and a User Plane Function (UPF) 158B,which are shown as one component AMF/UPF 158 in FIG. 1B for ease ofillustration. The UPF 158B may serve as a gateway between the NG-RAN 154and the one or more DNs. The UPF 158B may perform functions such aspacket routing and forwarding, packet inspection and user plane policyrule enforcement, traffic usage reporting, uplink classification tosupport routing of traffic flows to the one or more DNs, quality ofservice (QoS) handling for the user plane (e.g., packet filtering,gating, uplink/downlink rate enforcement, and uplink trafficverification), downlink packet buffering, and downlink data notificationtriggering. The UPF 158B may serve as an anchor point forintra-/inter-Radio Access Technology (RAT) mobility, an externalprotocol (or packet) data unit (PDU) session point of interconnect tothe one or more DNs, and/or a branching point to support a multi-homedPDU session. The UEs 156 may be configured to receive services through aPDU session, which is a logical connection between a UE and a DN.

The AMF 158A may perform functions such as Non-Access Stratum (NAS)signaling termination, NAS signaling security, Access Stratum (AS)security control, inter-CN node signaling for mobility between 3GPPaccess networks, idle mode UE reachability (e.g., control and executionof paging retransmission), registration area management, intra-systemand inter-system mobility support, access authentication, accessauthorization including checking of roaming rights, mobility managementcontrol (subscription and policies), network slicing support, and/orsession management function (SMF) selection. NAS may refer to thefunctionality operating between a CN and a UE, and AS may refer to thefunctionality operating between the UE and a RAN.

The 5G-CN 152 may include one or more additional network functions thatare not shown in FIG. 1B for the sake of clarity. For example, the 5G-CN152 may include one or more of a Session Management Function (SMF), anNR Repository Function (NRF), a Policy Control Function (PCF), a NetworkExposure Function (NEF), a Unified Data Management (UDM), an ApplicationFunction (AF), and/or an Authentication Server Function (AUSF).

The NG-RAN 154 may connect the 5G-CN 152 to the UEs 156 through radiocommunications over the air interface. The NG-RAN 154 may include one ormore gNBs, illustrated as gNB 160A and gNB 160B (collectively gNBs 160)and/or one or more ng-eNBs, illustrated as ng-eNB 162A and ng-eNB 162B(collectively ng-eNBs 162). The gNBs 160 and ng-eNBs 162 may be moregenerically referred to as base stations. The gNBs 160 and ng-eNBs 162may include one or more sets of antennas for communicating with the UEs156 over an air interface. For example, one or more of the gNBs 160and/or one or more of the ng-eNBs 162 may include three sets of antennasto respectively control three cells (or sectors). Together, the cells ofthe gNBs 160 and the ng-eNBs 162 may provide radio coverage to the UEs156 over a wide geographic area to support UE mobility.

As shown in FIG. 1B, the gNBs 160 and/or the ng-eNBs 162 may beconnected to the 5G-CN 152 by means of an NG interface and to other basestations by an Xn interface. The NG and Xn interfaces may be establishedusing direct physical connections and/or indirect connections over anunderlying transport network, such as an internet protocol (IP)transport network. The gNBs 160 and/or the ng-eNBs 162 may be connectedto the UEs 156 by means of a Uu interface. For example, as illustratedin FIG. 1B, gNB 160A may be connected to the UE 156A by means of a Uuinterface. The NG, Xn, and Uu interfaces are associated with a protocolstack. The protocol stacks associated with the interfaces may be used bythe network elements in FIG. 1B to exchange data and signaling messagesand may include two planes: a user plane and a control plane. The userplane may handle data of interest to a user. The control plane mayhandle signaling messages of interest to the network elements.

The gNBs 160 and/or the ng-eNBs 162 may be connected to one or moreAMF/UPF functions of the 5G-CN 152, such as the AMF/UPF 158, by means ofone or more NG interfaces. For example, the gNB 160A may be connected tothe UPF 158B of the AMF/UPF 158 by means of an NG-User plane (NG-U)interface. The NG-U interface may provide delivery (e.g., non-guaranteeddelivery) of user plane PDUs between the gNB 160A and the UPF 158B. ThegNB 160A may be connected to the AMF 158A by means of an NG-Controlplane (NG-C) interface. The NG-C interface may provide, for example, NGinterface management, UE context management, UE mobility management,transport of NAS messages, paging, PDU session management, andconfiguration transfer and/or warning message transmission.

The gNBs 160 may provide NR user plane and control plane protocolterminations towards the UEs 156 over the Uu interface. For example, thegNB 160A may provide NR user plane and control plane protocolterminations toward the UE 156A over a Uu interface associated with afirst protocol stack. The ng-eNBs 162 may provide Evolved UMTSTerrestrial Radio Access (E-UTRA) user plane and control plane protocolterminations towards the UEs 156 over a Uu interface, where E-UTRArefers to the 3GPP 4G radio-access technology. For example, the ng-eNB162B may provide E-UTRA user plane and control plane protocolterminations towards the UE 156B over a Uu interface associated with asecond protocol stack.

The 5G-CN 152 was described as being configured to handle NR and 4Gradio accesses. It will be appreciated by one of ordinary skill in theart that it may be possible for NR to connect to a 4G core network in amode known as “non-standalone operation.” In non-standalone operation, a4G core network is used to provide (or at least support) control-planefunctionality (e.g., initial access, mobility, and paging). Althoughonly one AMF/UPF 158 is shown in FIG. 1B, one gNB or ng-eNB may beconnected to multiple AMF/UPF nodes to provide redundancy and/or to loadshare across the multiple AMF/UPF nodes.

As discussed, an interface (e.g., Uu, Xn, and NG interfaces) between thenetwork elements in FIG. 1B may be associated with a protocol stack thatthe network elements use to exchange data and signaling messages. Aprotocol stack may include two planes: a user plane and a control plane.The user plane may handle data of interest to a user, and the controlplane may handle signaling messages of interest to the network elements.

FIG. 2A and FIG. 2B respectively illustrate examples of NR user planeand NR control plane protocol stacks for the Uu interface that liesbetween a UE 210 and a gNB 220. The protocol stacks illustrated in FIG.2A and FIG. 2B may be the same or similar to those used for the Uuinterface between, for example, the UE 156A and the gNB 160A shown inFIG. 1B.

FIG. 2A illustrates a NR user plane protocol stack comprising fivelayers implemented in the UE 210 and the gNB 220. At the bottom of theprotocol stack, physical layers (PHYs) 211 and 221 may provide transportservices to the higher layers of the protocol stack and may correspondto layer 1 of the Open Systems Interconnection (OSI) model. The nextfour protocols above PHYs 211 and 221 comprise media access controllayers (MACs) 212 and 222, radio link control layers (RLCs) 213 and 223,packet data convergence protocol layers (PDCPs) 214 and 224, and servicedata application protocol layers (SDAPs) 215 and 225. Together, thesefour protocols may make up layer 2, or the data link layer, of the OSImodel.

FIG. 3 illustrates an example of services provided between protocollayers of the NR user plane protocol stack. Starting from the top ofFIG. 2A and FIG. 3 , the SDAPs 215 and 225 may perform QoS flowhandling. The UE 210 may receive services through a PDU session, whichmay be a logical connection between the UE 210 and a DN. The PDU sessionmay have one or more QoS flows. A UPF of a CN (e.g., the UPF 158B) maymap IP packets to the one or more QoS flows of the PDU session based onQoS requirements (e.g., in terms of delay, data rate, and/or errorrate). The SDAPs 215 and 225 may perform mapping/de-mapping between theone or more QoS flows and one or more data radio bearers. Themapping/de-mapping between the QoS flows and the data radio bearers maybe determined by the SDAP 225 at the gNB 220. The SDAP 215 at the UE 210may be informed of the mapping between the QoS flows and the data radiobearers through reflective mapping or control signaling received fromthe gNB 220. For reflective mapping, the SDAP 225 at the gNB 220 maymark the downlink packets with a QoS flow indicator (QFI), which may beobserved by the SDAP 215 at the UE 210 to determine themapping/de-mapping between the QoS flows and the data radio bearers.

The PDCPs 214 and 224 may perform header compression/decompression toreduce the amount of data that needs to be transmitted over the airinterface, ciphering/deciphering to prevent unauthorized decoding ofdata transmitted over the air interface, and integrity protection (toensure control messages originate from intended sources. The PDCPs 214and 224 may perform retransmissions of undelivered packets, in-sequencedelivery and reordering of packets, and removal of packets received induplicate due to, for example, an intra-gNB handover. The PDCPs 214 and224 may perform packet duplication to improve the likelihood of thepacket being received and, at the receiver, remove any duplicatepackets. Packet duplication may be useful for services that require highreliability.

Although not shown in FIG. 3 , PDCPs 214 and 224 may performmapping/de-mapping between a split radio bearer and RLC channels in adual connectivity scenario. Dual connectivity is a technique that allowsa UE to connect to two cells or, more generally, two cell groups: amaster cell group (MCG) and a secondary cell group (SCG). A split beareris when a single radio bearer, such as one of the radio bearers providedby the PDCPs 214 and 224 as a service to the SDAPs 215 and 225, ishandled by cell groups in dual connectivity. The PDCPs 214 and 224 maymap/de-map the split radio bearer between RLC channels belonging to cellgroups.

The RLCs 213 and 223 may perform segmentation, retransmission throughAutomatic Repeat Request (ARQ), and removal of duplicate data unitsreceived from MACs 212 and 222, respectively. The RLCs 213 and 223 maysupport three transmission modes: transparent mode (TM); unacknowledgedmode (UM); and acknowledged mode (AM). Based on the transmission mode anRLC is operating, the RLC may perform one or more of the notedfunctions. The RLC configuration may be per logical channel with nodependency on numerologies and/or Transmission Time Interval (TTI)durations. As shown in FIG. 3 , the RLCs 213 and 223 may provide RLCchannels as a service to PDCPs 214 and 224, respectively.

The MACs 212 and 222 may perform multiplexing/demultiplexing of logicalchannels and/or mapping between logical channels and transport channels.The multiplexing/demultiplexing may include multiplexing/demultiplexingof data units, belonging to the one or more logical channels, into/fromTransport Blocks (TBs) delivered to/from the PHYs 211 and 221. The MAC222 may be configured to perform scheduling, scheduling informationreporting, and priority handling between UEs by means of dynamicscheduling. Scheduling may be performed in the gNB 220 (at the MAC 222)for downlink and uplink. The MACs 212 and 222 may be configured toperform error correction through Hybrid Automatic Repeat Request (HARQ)(e.g., one HARQ entity per carrier in case of Carrier Aggregation (CA)),priority handling between logical channels of the UE 210 by means oflogical channel prioritization, and/or padding. The MACs 212 and 222 maysupport one or more numerologies and/or transmission timings. In anexample, mapping restrictions in a logical channel prioritization maycontrol which numerology and/or transmission timing a logical channelmay use. As shown in FIG. 3 , the MACs 212 and 222 may provide logicalchannels as a service to the RLCs 213 and 223.

The PHYs 211 and 221 may perform mapping of transport channels tophysical channels and digital and analog signal processing functions forsending and receiving information over the air interface. These digitaland analog signal processing functions may include, for example,coding/decoding and modulation/demodulation. The PHYs 211 and 221 mayperform multi-antenna mapping. As shown in FIG. 3 , the PHYs 211 and 221may provide one or more transport channels as a service to the MACs 212and 222.

FIG. 4A illustrates an example downlink data flow through the NR userplane protocol stack. FIG. 4A illustrates a downlink data flow of threeIP packets (n, n+1, and m) through the NR user plane protocol stack togenerate two TBs at the gNB 220. An uplink data flow through the NR userplane protocol stack may be similar to the downlink data flow depictedin FIG. 4A.

The downlink data flow of FIG. 4A begins when SDAP 225 receives thethree IP packets from one or more QoS flows and maps the three packetsto radio bearers. In FIG. 4A, the SDAP 225 maps IP packets n and n+1 toa first radio bearer 402 and maps IP packet m to a second radio bearer404. An SDAP header (labeled with an “H” in FIG. 4A) is added to an IPpacket. The data unit from/to a higher protocol layer is referred to asa service data unit (SDU) of the lower protocol layer and the data unitto/from a lower protocol layer is referred to as a protocol data unit(PDU) of the higher protocol layer. As shown in FIG. 4A, the data unitfrom the SDAP 225 is an SDU of lower protocol layer PDCP 224 and is aPDU of the SDAP 225.

The remaining protocol layers in FIG. 4A may perform their associatedfunctionality (e.g., with respect to FIG. 3 ), add correspondingheaders, and forward their respective outputs to the next lower layer.For example, the PDCP 224 may perform IP-header compression andciphering and forward its output to the RLC 223. The RLC 223 mayoptionally perform segmentation (e.g., as shown for IP packet m in FIG.4A) and forward its output to the MAC 222. The MAC 222 may multiplex anumber of RLC PDUs and may attach a MAC subheader to an RLC PDU to forma transport block. In NR, the MAC subheaders may be distributed acrossthe MAC PDU, as illustrated in FIG. 4A. In LTE, the MAC subheaders maybe entirely located at the beginning of the MAC PDU. The NR MAC PDUstructure may reduce processing time and associated latency because theMAC PDU subheaders may be computed before the full MAC PDU is assembled.

FIG. 4B illustrates an example format of a MAC subheader in a MAC PDU.The MAC subheader includes: an SDU length field for indicating thelength (e.g., in bytes) of the MAC SDU to which the MAC subheadercorresponds; a logical channel identifier (LCID) field for identifyingthe logical channel from which the MAC SDU originated to aid in thedemultiplexing process; a flag (F) for indicating the size of the SDUlength field; and a reserved bit (R) field for future use.

FIG. 4B further illustrates MAC control elements (CEs) inserted into theMAC PDU by a MAC, such as MAC 212 or MAC 222. For example, FIG. 4Billustrates two MAC CEs inserted into the MAC PDU. MAC CEs may beinserted at the beginning of a MAC PDU for downlink transmissions (asshown in FIG. 4B) and at the end of a MAC PDU for uplink transmissions.MAC CEs may be used for in-band control signaling. Example MAC CEsinclude: scheduling-related MAC CEs, such as buffer status reports andpower headroom reports; activation/deactivation MAC CEs, such as thosefor activation/deactivation of PDCP duplication detection, channel stateinformation (CSI) reporting, sounding reference signal (SRS)transmission, and prior configured components; discontinuous reception(DRX) related MAC CEs; timing advance MAC CEs; and random access relatedMAC CEs. A MAC CE may be preceded by a MAC subheader with a similarformat as described for MAC SDUs and may be identified with a reservedvalue in the LCID field that indicates the type of control informationincluded in the MAC CE.

Before describing the NR control plane protocol stack, logical channels,transport channels, and physical channels are first described as well asa mapping between the channel types. One or more of the channels may beused to carry out functions associated with the NR control planeprotocol stack described later below.

FIG. 5A and FIG. 5B illustrate, for downlink and uplink respectively, amapping between logical channels, transport channels, and physicalchannels. Information is passed through channels between the RLC, theMAC, and the PHY of the NR protocol stack. A logical channel may be usedbetween the RLC and the MAC and may be classified as a control channelthat carries control and configuration information in the NR controlplane or as a traffic channel that carries data in the NR user plane. Alogical channel may be classified as a dedicated logical channel that isdedicated to a specific UE or as a common logical channel that may beused by more than one UE. A logical channel may also be defined by thetype of information it carries. The set of logical channels defined byNR include, for example:

-   -   a paging control channel (PCCH) for carrying paging messages        used to page a UE whose location is not known to the network on        a cell level;    -   a broadcast control channel (BCCH) for carrying system        information messages in the form of a master information block        (MIB) and several system information blocks (SIBs), wherein the        system information messages may be used by the UEs to obtain        information about how a cell is configured and how to operate        within the cell;    -   a common control channel (CCCH) for carrying control messages        together with random access;    -   a dedicated control channel (DCCH) for carrying control messages        to/from a specific the UE to configure the UE; and    -   a dedicated traffic channel (DTCH) for carrying user data        to/from a specific the UE.

Transport channels are used between the MAC and PHY layers and may bedefined by how the information they carry is transmitted over the airinterface. The set of transport channels defined by NR include, forexample:

-   -   a paging channel (PCH) for carrying paging messages that        originated from the PCCH;    -   a broadcast channel (BCH) for carrying the MIB from the BCCH;    -   a downlink shared channel (DL-SCH) for carrying downlink data        and signaling messages, including the SIBs from the BCCH;    -   an uplink shared channel (UL-SCH) for carrying uplink data and        signaling messages; and    -   a random access channel (RACH) for allowing a UE to contact the        network without any prior scheduling.

The PHY may use physical channels to pass information between processinglevels of the PHY. A physical channel may have an associated set oftime-frequency resources for carrying the information of one or moretransport channels. The PHY may generate control information to supportthe low-level operation of the PHY and provide the control informationto the lower levels of the PHY via physical control channels, known asL1/L2 control channels. The set of physical channels and physicalcontrol channels defined by NR include, for example:

-   -   a physical broadcast channel (PBCH) for carrying the MIB from        the BCH;    -   a physical downlink shared channel (PDSCH) for carrying downlink        data and signaling messages from the DL-SCH, as well as paging        messages from the PCH;    -   a physical downlink control channel (PDCCH) for carrying        downlink control information (DCI), which may include downlink        scheduling commands, uplink scheduling grants, and uplink power        control commands;    -   a physical uplink shared channel (PUSCH) for carrying uplink        data and signaling messages from the UL-SCH and in some        instances uplink control information (UCI) as described below;    -   a physical uplink control channel (PUCCH) for carrying UCI,        which may include HARQ acknowledgments, channel quality        indicators (CQI), pre-coding matrix indicators (PMI), rank        indicators (RI), and scheduling requests (SR); and    -   a physical random access channel (PRACH) for random access.

Similar to the physical control channels, the physical layer generatesphysical signals to support the low-level operation of the physicallayer. As shown in FIG. 5A and FIG. 5B, the physical layer signalsdefined by NR include: primary synchronization signals (PSS), secondarysynchronization signals (SSS), channel state information referencesignals (CSI-RS), demodulation reference signals (DMRS), soundingreference signals (SRS), and phase-tracking reference signals (PT-RS).These physical layer signals will be described in greater detail below.

FIG. 2B illustrates an example NR control plane protocol stack. As shownin FIG. 2B, the NR control plane protocol stack may use the same/similarfirst four protocol layers as the example NR user plane protocol stack.These four protocol layers include the PHYs 211 and 221, the MACs 212and 222, the RLCs 213 and 223, and the PDCPs 214 and 224. Instead ofhaving the SDAPs 215 and 225 at the top of the stack as in the NR userplane protocol stack, the NR control plane stack has radio resourcecontrols (RRCs) 216 and 226 and NAS protocols 217 and 237 at the top ofthe NR control plane protocol stack.

The NAS protocols 217 and 237 may provide control plane functionalitybetween the UE 210 and the AMF 230 (e.g., the AMF 158A) or, moregenerally, between the UE 210 and the CN. The NAS protocols 217 and 237may provide control plane functionality between the UE 210 and the AMF230 via signaling messages, referred to as NAS messages. There is nodirect path between the UE 210 and the AMF 230 through which the NASmessages can be transported. The NAS messages may be transported usingthe AS of the Uu and NG interfaces. NAS protocols 217 and 237 mayprovide control plane functionality such as authentication, security,connection setup, mobility management, and session management.

The RRCs 216 and 226 may provide control plane functionality between theUE 210 and the gNB 220 or, more generally, between the UE 210 and theRAN. The RRCs 216 and 226 may provide control plane functionalitybetween the UE 210 and the gNB 220 via signaling messages, referred toas RRC messages. RRC messages may be transmitted between the UE 210 andthe RAN using signaling radio bearers and the same/similar PDCP, RLC,MAC, and PHY protocol layers. The MAC may multiplex control-plane anduser-plane data into the same transport block (TB). The RRCs 216 and 226may provide control plane functionality such as: broadcast of systeminformation related to AS and NAS; paging initiated by the CN or theRAN; establishment, maintenance and release of an RRC connection betweenthe UE 210 and the RAN; security functions including key management;establishment, configuration, maintenance and release of signaling radiobearers and data radio bearers; mobility functions; QoS managementfunctions; the UE measurement reporting and control of the reporting;detection of and recovery from radio link failure (RLF); and/or NASmessage transfer. As part of establishing an RRC connection, RRCs 216and 226 may establish an RRC context, which may involve configuringparameters for communication between the UE 210 and the RAN.

FIG. 6 is an example diagram showing RRC state transitions of a UE. TheUE may be the same or similar to the wireless device 106 depicted inFIG. 1A, the UE 210 depicted in FIG. 2A and FIG. 2B, or any otherwireless device described in the present disclosure. As illustrated inFIG. 6 , a UE may be in at least one of three RRC states: RRC connected602 (e.g., RRC_CONNECTED), RRC idle 604 (e.g., RRC_IDLE), and RRCinactive 606 (e.g., RRC_INACTIVE).

In RRC connected 602, the UE has an established RRC context and may haveat least one RRC connection with a base station. The base station may besimilar to one of the one or more base stations included in the RAN 104depicted in FIG. 1A, one of the gNBs 160 or ng-eNBs 162 depicted in FIG.1B, the gNB 220 depicted in FIG. 2A and FIG. 2B, or any other basestation described in the present disclosure. The base station with whichthe UE is connected may have the RRC context for the UE. The RRCcontext, referred to as the UE context, may comprise parameters forcommunication between the UE and the base station. These parameters mayinclude, for example: one or more AS contexts; one or more radio linkconfiguration parameters; bearer configuration information (e.g.,relating to a data radio bearer, signaling radio bearer, logicalchannel, QoS flow, and/or PDU session); security information; and/orPHY, MAC, RLC, PDCP, and/or SDAP layer configuration information. Whilein RRC connected 602, mobility of the UE may be managed by the RAN(e.g., the RAN 104 or the NG-RAN 154). The UE may measure the signallevels (e.g., reference signal levels) from a serving cell andneighboring cells and report these measurements to the base stationcurrently serving the UE. The UE's serving base station may request ahandover to a cell of one of the neighboring base stations based on thereported measurements. The RRC state may transition from RRC connected602 to RRC idle 604 through a connection release procedure 608 or to RRCinactive 606 through a connection inactivation procedure 610.

In RRC idle 604, an RRC context may not be established for the UE. InRRC idle 604, the UE may not have an RRC connection with the basestation. While in RRC idle 604, the UE may be in a sleep state for themajority of the time (e.g., to conserve battery power). The UE may wakeup periodically (e.g., once in every discontinuous reception cycle) tomonitor for paging messages from the RAN. Mobility of the UE may bemanaged by the UE through a procedure known as cell reselection. The RRCstate may transition from RRC idle 604 to RRC connected 602 through aconnection establishment procedure 612, which may involve a randomaccess procedure as discussed in greater detail below.

In RRC inactive 606, the RRC context previously established ismaintained in the UE and the base station. This allows for a fasttransition to RRC connected 602 with reduced signaling overhead ascompared to the transition from RRC idle 604 to RRC connected 602. Whilein RRC inactive 606, the UE may be in a sleep state and mobility of theUE may be managed by the UE through cell reselection. The RRC state maytransition from RRC inactive 606 to RRC connected 602 through aconnection resume procedure 614 or to RRC idle 604 though a connectionrelease procedure 616 that may be the same as or similar to connectionrelease procedure 608.

An RRC state may be associated with a mobility management mechanism. InRRC idle 604 and RRC inactive 606, mobility is managed by the UE throughcell reselection. The purpose of mobility management in RRC idle 604 andRRC inactive 606 is to allow the network to be able to notify the UE ofan event via a paging message without having to broadcast the pagingmessage over the entire mobile communications network. The mobilitymanagement mechanism used in RRC idle 604 and RRC inactive 606 may allowthe network to track the UE on a cell-group level so that the pagingmessage may be broadcast over the cells of the cell group that the UEcurrently resides within instead of the entire mobile communicationnetwork. The mobility management mechanisms for RRC idle 604 and RRCinactive 606 track the UE on a cell-group level. They may do so usingdifferent granularities of grouping. For example, there may be threelevels of cell-grouping granularity: individual cells; cells within aRAN area identified by a RAN area identifier (RAI); and cells within agroup of RAN areas, referred to as a tracking area and identified by atracking area identifier (TAI).

Tracking areas may be used to track the UE at the CN level. The CN(e.g., the CN 102 or the 5G-CN 152) may provide the UE with a list ofTAIs associated with a UE registration area. If the UE moves, throughcell reselection, to a cell associated with a TAI not included in thelist of TAIs associated with the UE registration area, the UE mayperform a registration update with the CN to allow the CN to update theUE's location and provide the UE with a new the UE registration area.

RAN areas may be used to track the UE at the RAN level. For a UE in RRCinactive 606 state, the UE may be assigned a RAN notification area. ARAN notification area may comprise one or more cell identities, a listof RAIs, or a list of TAIs. In an example, a base station may belong toone or more RAN notification areas. In an example, a cell may belong toone or more RAN notification areas. If the UE moves, through cellreselection, to a cell not included in the RAN notification areaassigned to the UE, the UE may perform a notification area update withthe RAN to update the UE's RAN notification area.

A base station storing an RRC context for a UE or a last serving basestation of the UE may be referred to as an anchor base station. Ananchor base station may maintain an RRC context for the UE at leastduring a period of time that the UE stays in a RAN notification area ofthe anchor base station and/or during a period of time that the UE staysin RRC inactive 606.

A gNB, such as gNBs 160 in FIG. 1B, may be split in two parts: a centralunit (gNB-CU), and one or more distributed units (gNB-DU). A gNB-CU maybe coupled to one or more gNB-DUs using an F1 interface. The gNB-CU maycomprise the RRC, the PDCP, and the SDAP. A gNB-DU may comprise the RLC,the MAC, and the PHY.

In NR, the physical signals and physical channels (discussed withrespect to FIG. 5A and FIG. 5B) may be mapped onto orthogonal frequencydivisional multiplexing (OFDM) symbols. OFDM is a multicarriercommunication scheme that transmits data over F orthogonal subcarriers(or tones). Before transmission, the data may be mapped to a series ofcomplex symbols (e.g., M-quadrature amplitude modulation (M-QAM) orM-phase shift keying (M-PSK) symbols), referred to as source symbols,and divided into F parallel symbol streams. The F parallel symbolstreams may be treated as though they are in the frequency domain andused as inputs to an Inverse Fast Fourier Transform (IFFT) block thattransforms them into the time domain. The IFFT block may take in Fsource symbols at a time, one from each of the F parallel symbolstreams, and use each source symbol to modulate the amplitude and phaseof one of F sinusoidal basis functions that correspond to the Forthogonal subcarriers. The output of the IFFT block may be Ftime-domain samples that represent the summation of the F orthogonalsubcarriers. The F time-domain samples may form a single OFDM symbol.After some processing (e.g., addition of a cyclic prefix) andup-conversion, an OFDM symbol provided by the IFFT block may betransmitted over the air interface on a carrier frequency. The Fparallel symbol streams may be mixed using an FFT block before beingprocessed by the IFFT block. This operation produces Discrete FourierTransform (DFT)-precoded OFDM symbols and may be used by UEs in theuplink to reduce the peak to average power ratio (PAPR). Inverseprocessing may be performed on the OFDM symbol at a receiver using anFFT block to recover the data mapped to the source symbols.

FIG. 7 illustrates an example configuration of an NR frame into whichOFDM symbols are grouped. An NR frame may be identified by a systemframe number (SFN). The SFN may repeat with a period of 1024 frames. Asillustrated, one NR frame may be 10 milliseconds (ms) in duration andmay include 10 subframes that are 1 ms in duration. A subframe may bedivided into slots that include, for example, 14 OFDM symbols per slot.

The duration of a slot may depend on the numerology used for the OFDMsymbols of the slot. In NR, a flexible numerology is supported toaccommodate different cell deployments (e.g., cells with carrierfrequencies below 1 GHz up to cells with carrier frequencies in themm-wave range). A numerology may be defined in terms of subcarrierspacing and cyclic prefix duration. For a numerology in NR, subcarrierspacings may be scaled up by powers of two from a baseline subcarrierspacing of 15 kHz, and cyclic prefix durations may be scaled down bypowers of two from a baseline cyclic prefix duration of 4.7 μs. Forexample, NR defines numerologies with the following subcarrierspacing/cyclic prefix duration combinations: 15 kHz/4.7 μs; 30 kHz/2.3μs; 60 kHz/1.2 μs; 120 kHz/0.59 μs; and 240 kHz/0.29 μs.

A slot may have a fixed number of OFDM symbols (e.g., 14 OFDM symbols).A numerology with a higher subcarrier spacing has a shorter slotduration and, correspondingly, more slots per subframe. FIG. 7illustrates this numerology-dependent slot duration andslots-per-subframe transmission structure (the numerology with asubcarrier spacing of 240 kHz is not shown in FIG. 7 for ease ofillustration). A subframe in NR may be used as a numerology-independenttime reference, while a slot may be used as the unit upon which uplinkand downlink transmissions are scheduled. To support low latency,scheduling in NR may be decoupled from the slot duration and start atany OFDM symbol and last for as many symbols as needed for atransmission. These partial slot transmissions may be referred to asmini-slot or subslot transmissions.

FIG. 8 illustrates an example configuration of a slot in the time andfrequency domain for an NR carrier. The slot includes resource elements(REs) and resource blocks (RBs). An RE is the smallest physical resourcein NR. An RE spans one OFDM symbol in the time domain by one subcarrierin the frequency domain as shown in FIG. 8 . An RB spans twelveconsecutive REs in the frequency domain as shown in FIG. 8 . An NRcarrier may be limited to a width of 275 RBs or 275×12=3300 subcarriers.Such a limitation, if used, may limit the NR carrier to 50, 100, 200,and 400 MHz for subcarrier spacings of 15, 30, 60, and 120 kHz,respectively, where the 400 MHz bandwidth may be set based on a 400 MHzper carrier bandwidth limit.

FIG. 8 illustrates a single numerology being used across the entirebandwidth of the NR carrier. In other example configurations, multiplenumerologies may be supported on the same carrier.

NR may support wide carrier bandwidths (e.g., up to 400 MHz for asubcarrier spacing of 120 kHz). Not all UEs may be able to receive thefull carrier bandwidth (e.g., due to hardware limitations). Also,receiving the full carrier bandwidth may be prohibitive in terms of UEpower consumption. In an example, to reduce power consumption and/or forother purposes, a UE may adapt the size of the UE's receive bandwidthbased on the amount of traffic the UE is scheduled to receive. This isreferred to as bandwidth adaptation.

NR defines bandwidth parts (BWPs) to support UEs not capable ofreceiving the full carrier bandwidth and to support bandwidthadaptation. In an example, a BWP may be defined by a subset ofcontiguous RBs on a carrier. A UE may be configured (e.g., via RRClayer) with one or more downlink BWPs and one or more uplink BWPs perserving cell (e.g., up to four downlink BWPs and up to four uplink BWPsper serving cell). At a given time, one or more of the configured BWPsfor a serving cell may be active. These one or more BWPs may be referredto as active BWPs of the serving cell. When a serving cell is configuredwith a secondary uplink carrier, the serving cell may have one or morefirst active BWPs in the uplink carrier and one or more second activeBWPs in the secondary uplink carrier.

For unpaired spectra, a downlink BWP from a set of configured downlinkBWPs may be linked with an uplink BWP from a set of configured uplinkBWPs if a downlink BWP index of the downlink BWP and an uplink BWP indexof the uplink BWP are the same. For unpaired spectra, a UE may expectthat a center frequency for a downlink BWP is the same as a centerfrequency for an uplink BWP.

For a downlink BWP in a set of configured downlink BWPs on a primarycell (PCell), a base station may configure a UE with one or more controlresource sets (CORESETs) for at least one search space. A search spaceis a set of locations in the time and frequency domains where the UE mayfind control information. The search space may be a UE-specific searchspace or a common search space (potentially usable by a plurality ofUEs). For example, a base station may configure a UE with a commonsearch space, on a PCell or on a primary secondary cell (PSCell), in anactive downlink BWP.

For an uplink BWP in a set of configured uplink BWPs, a BS may configurea UE with one or more resource sets for one or more PUCCH transmissions.A UE may receive downlink receptions (e.g., PDCCH or PDSCH) in adownlink BWP according to a configured numerology (e.g., subcarrierspacing and cyclic prefix duration) for the downlink BWP. The UE maytransmit uplink transmissions (e.g., PUCCH or PUSCH) in an uplink BWPaccording to a configured numerology (e.g., subcarrier spacing andcyclic prefix length for the uplink BWP).

One or more BWP indicator fields may be provided in Downlink ControlInformation (DCI). A value of a BWP indicator field may indicate whichBWP in a set of configured BWPs is an active downlink BWP for one ormore downlink receptions. The value of the one or more BWP indicatorfields may indicate an active uplink BWP for one or more uplinktransmissions.

A base station may semi-statically configure a UE with a defaultdownlink BWP within a set of configured downlink BWPs associated with aPCell. If the base station does not provide the default downlink BWP tothe UE, the default downlink BWP may be an initial active downlink BWP.The UE may determine which BWP is the initial active downlink BWP basedon a CORESET configuration obtained using the PBCH.

A base station may configure a UE with a BWP inactivity timer value fora PCell. The UE may start or restart a BWP inactivity timer at anyappropriate time. For example, the UE may start or restart the BWPinactivity timer (a) when the UE detects a DCI indicating an activedownlink BWP other than a default downlink BWP for a paired spectraoperation; or (b) when a UE detects a DCI indicating an active downlinkBWP or active uplink BWP other than a default downlink BWP or uplink BWPfor an unpaired spectra operation. If the UE does not detect DCI duringan interval of time (e.g., 1 ms or 0.5 ms), the UE may run the BWPinactivity timer toward expiration (for example, increment from zero tothe BWP inactivity timer value, or decrement from the BWP inactivitytimer value to zero). When the BWP inactivity timer expires, the UE mayswitch from the active downlink BWP to the default downlink BWP.

In an example, a base station may semi-statically configure a UE withone or more BWPs. A UE may switch an active BWP from a first BWP to asecond BWP in response to receiving a DCI indicating the second BWP asan active BWP and/or in response to an expiry of the BWP inactivitytimer (e.g., if the second BWP is the default BWP).

Downlink and uplink BWP switching (where BWP switching refers toswitching from a currently active BWP to a not currently active BWP) maybe performed independently in paired spectra. In unpaired spectra,downlink and uplink BWP switching may be performed simultaneously.Switching between configured BWPs may occur based on RRC signaling, DCI,expiration of a BWP inactivity timer, and/or an initiation of randomaccess.

FIG. 9 illustrates an example of bandwidth adaptation using threeconfigured BWPs for an NR carrier. A UE configured with the three BWPsmay switch from one BWP to another BWP at a switching point. In theexample illustrated in FIG. 9 , the BWPs include: a BWP 902 with abandwidth of 40 MHz and a subcarrier spacing of 15 kHz; a BWP 904 with abandwidth of 10 MHz and a subcarrier spacing of 15 kHz; and a BWP 906with a bandwidth of 20 MHz and a subcarrier spacing of 60 kHz. The BWP902 may be an initial active BWP, and the BWP 904 may be a default BWP.The UE may switch between BWPs at switching points. In the example ofFIG. 9 , the UE may switch from the BWP 902 to the BWP 904 at aswitching point 908. The switching at the switching point 908 may occurfor any suitable reason, for example, in response to an expiry of a BWPinactivity timer (indicating switching to the default BWP) and/or inresponse to receiving a DCI indicating BWP 904 as the active BWP. The UEmay switch at a switching point 910 from active BWP 904 to BWP 906 inresponse receiving a DCI indicating BWP 906 as the active BWP. The UEmay switch at a switching point 912 from active BWP 906 to BWP 904 inresponse to an expiry of a BWP inactivity timer and/or in responsereceiving a DCI indicating BWP 904 as the active BWP. The UE may switchat a switching point 914 from active BWP 904 to BWP 902 in responsereceiving a DCI indicating BWP 902 as the active BWP.

If a UE is configured for a secondary cell with a default downlink BWPin a set of configured downlink BWPs and a timer value, UE proceduresfor switching BWPs on a secondary cell may be the same/similar as thoseon a primary cell. For example, the UE may use the timer value and thedefault downlink BWP for the secondary cell in the same/similar manneras the UE would use these values for a primary cell.

To provide for greater data rates, two or more carriers can beaggregated and simultaneously transmitted to/from the same UE usingcarrier aggregation (CA). The aggregated carriers in CA may be referredto as component carriers (CCs). When CA is used, there are a number ofserving cells for the UE, one for a CC. The CCs may have threeconfigurations in the frequency domain.

FIG. 10A illustrates the three CA configurations with two CCs. In theintraband, contiguous configuration 1002, the two CCs are aggregated inthe same frequency band (frequency band A) and are located directlyadjacent to each other within the frequency band. In the intraband,non-contiguous configuration 1004, the two CCs are aggregated in thesame frequency band (frequency band A) and are separated in thefrequency band by a gap. In the interband configuration 1006, the twoCCs are located in frequency bands (frequency band A and frequency bandB).

In an example, up to 32 CCs may be aggregated. The aggregated CCs mayhave the same or different bandwidths, subcarrier spacing, and/orduplexing schemes (TDD or FDD). A serving cell for a UE using CA mayhave a downlink CC. For FDD, one or more uplink CCs may be optionallyconfigured for a serving cell. The ability to aggregate more downlinkcarriers than uplink carriers may be useful, for example, when the UEhas more data traffic in the downlink than in the uplink.

When CA is used, one of the aggregated cells for a UE may be referred toas a primary cell (PCell). The PCell may be the serving cell that the UEinitially connects to at RRC connection establishment, reestablishment,and/or handover. The PCell may provide the UE with NAS mobilityinformation and the security input. UEs may have different PCells. Inthe downlink, the carrier corresponding to the PCell may be referred toas the downlink primary CC (DL PCC). In the uplink, the carriercorresponding to the PCell may be referred to as the uplink primary CC(UL PCC). The other aggregated cells for the UE may be referred to assecondary cells (SCells). In an example, the SCells may be configuredafter the PCell is configured for the UE. For example, an SCell may beconfigured through an RRC Connection Reconfiguration procedure. In thedownlink, the carrier corresponding to an SCell may be referred to as adownlink secondary CC (DL SCC). In the uplink, the carrier correspondingto the SCell may be referred to as the uplink secondary CC (UL SCC).

Configured SCells for a UE may be activated and deactivated based on,for example, traffic and channel conditions. Deactivation of an SCellmay mean that PDCCH and PDSCH reception on the SCell is stopped andPUSCH, SRS, and CQI transmissions on the SCell are stopped. ConfiguredSCells may be activated and deactivated using a MAC CE with respect toFIG. 4B. For example, a MAC CE may use a bitmap (e.g., one bit perSCell) to indicate which SCells (e.g., in a subset of configured SCells)for the UE are activated or deactivated. Configured SCells may bedeactivated in response to an expiration of an SCell deactivation timer(e.g., one SCell deactivation timer per SCell).

Downlink control information, such as scheduling assignments andscheduling grants, for a cell may be transmitted on the cellcorresponding to the assignments and grants, which is known asself-scheduling. The DCI for the cell may be transmitted on anothercell, which is known as cross-carrier scheduling. Uplink controlinformation (e.g., HARQ acknowledgments and channel state feedback, suchas CQI, PMI, and/or RI) for aggregated cells may be transmitted on thePUCCH of the PCell. For a larger number of aggregated downlink CCs, thePUCCH of the PCell may become overloaded. Cells may be divided intomultiple PUCCH groups.

FIG. 10B illustrates an example of how aggregated cells may beconfigured into one or more PUCCH groups. A PUCCH group 1010 and a PUCCHgroup 1050 may include one or more downlink CCs, respectively. In theexample of FIG. 10B, the PUCCH group 1010 includes three downlink CCs: aPCell 1011, an SCell 1012, and an SCell 1013. The PUCCH group 1050includes three downlink CCs in the present example: a PCell 1051, anSCell 1052, and an SCell 1053. One or more uplink CCs may be configuredas a PCell 1021, an SCell 1022, and an SCell 1023. One or more otheruplink CCs may be configured as a primary Scell (PSCell) 1061, an SCell1062, and an SCell 1063. Uplink control information (UCI) related to thedownlink CCs of the PUCCH group 1010, shown as UCI 1031, UCI 1032, andUCI 1033, may be transmitted in the uplink of the PCell 1021. Uplinkcontrol information (UCI) related to the downlink CCs of the PUCCH group1050, shown as UCI 1071, UCI 1072, and UCI 1073, may be transmitted inthe uplink of the PSCell 1061. In an example, if the aggregated cellsdepicted in FIG. 10B were not divided into the PUCCH group 1010 and thePUCCH group 1050, a single uplink PCell to transmit UCI relating to thedownlink CCs, and the PCell may become overloaded. By dividingtransmissions of UCI between the PCell 1021 and the PSCell 1061,overloading may be prevented.

A cell, comprising a downlink carrier and optionally an uplink carrier,may be assigned with a physical cell ID and a cell index. The physicalcell ID or the cell index may identify a downlink carrier and/or anuplink carrier of the cell, for example, depending on the context inwhich the physical cell ID is used. A physical cell ID may be determinedusing a synchronization signal transmitted on a downlink componentcarrier. A cell index may be determined using RRC messages. In thedisclosure, a physical cell ID may be referred to as a carrier ID, and acell index may be referred to as a carrier index. For example, when thedisclosure refers to a first physical cell ID for a first downlinkcarrier, the disclosure may mean the first physical cell ID is for acell comprising the first downlink carrier. The same/similar concept mayapply to, for example, a carrier activation. When the disclosureindicates that a first carrier is activated, the specification may meanthat a cell comprising the first carrier is activated.

In CA, a multi-carrier nature of a PHY may be exposed to a MAC. In anexample, a HARQ entity may operate on a serving cell. A transport blockmay be generated per assignment/grant per serving cell. A transportblock and potential HARQ retransmissions of the transport block may bemapped to a serving cell.

In the downlink, a base station may transmit (e.g., unicast, multicast,and/or broadcast) one or more Reference Signals (RSs) to a UE (e.g.,PSS, SSS, CSI-RS, DMRS, and/or PT-RS, as shown in FIG. 5A). In theuplink, the UE may transmit one or more RSs to the base station (e.g.,DMRS, PT-RS, and/or SRS, as shown in FIG. 5B). The PSS and the SSS maybe transmitted by the base station and used by the UE to synchronize theUE to the base station. The PSS and the SSS may be provided in asynchronization signal (SS)/physical broadcast channel (PBCH) block thatincludes the PSS, the SSS, and the PBCH. The base station mayperiodically transmit a burst of SS/PBCH blocks.

FIG. 11A illustrates an example of an SS/PBCH block's structure andlocation. A burst of SS/PBCH blocks may include one or more SS/PBCHblocks (e.g., 4 SS/PBCH blocks, as shown in FIG. 11A). Bursts may betransmitted periodically (e.g., every 2 frames or 20 ms). A burst may berestricted to a half-frame (e.g., a first half-frame having a durationof 5 ms). It will be understood that FIG. 11A is an example, and thatthese parameters (number of SS/PBCH blocks per burst, periodicity ofbursts, position of burst within the frame) may be configured based on,for example: a carrier frequency of a cell in which the SS/PBCH block istransmitted; a numerology or subcarrier spacing of the cell; aconfiguration by the network (e.g., using RRC signaling); or any othersuitable factor. In an example, the UE may assume a subcarrier spacingfor the SS/PBCH block based on the carrier frequency being monitored,unless the radio network configured the UE to assume a differentsubcarrier spacing.

The SS/PBCH block may span one or more OFDM symbols in the time domain(e.g., 4 OFDM symbols, as shown in the example of FIG. 11A) and may spanone or more subcarriers in the frequency domain (e.g., 240 contiguoussubcarriers). The PSS, the SSS, and the PBCH may have a common centerfrequency. The PSS may be transmitted first and may span, for example, 1OFDM symbol and 127 subcarriers. The SSS may be transmitted after thePSS (e.g., two symbols later) and may span 1 OFDM symbol and 127subcarriers. The PBCH may be transmitted after the PSS (e.g., across thenext 3 OFDM symbols) and may span 240 subcarriers.

The location of the SS/PBCH block in the time and frequency domains maynot be known to the UE (e.g., if the UE is searching for the cell). Tofind and select the cell, the UE may monitor a carrier for the PSS. Forexample, the UE may monitor a frequency location within the carrier. Ifthe PSS is not found after a certain duration (e.g., 20 ms), the UE maysearch for the PSS at a different frequency location within the carrier,as indicated by a synchronization raster. If the PSS is found at alocation in the time and frequency domains, the UE may determine, basedon a known structure of the SS/PBCH block, the locations of the SSS andthe PBCH, respectively. The SS/PBCH block may be a cell-defining SSblock (CD-SSB). In an example, a primary cell may be associated with aCD-SSB. The CD-SSB may be located on a synchronization raster. In anexample, a cell selection/search and/or reselection may be based on theCD-SSB.

The SS/PBCH block may be used by the UE to determine one or moreparameters of the cell. For example, the UE may determine a physicalcell identifier (PCI) of the cell based on the sequences of the PSS andthe SSS, respectively. The UE may determine a location of a frameboundary of the cell based on the location of the SS/PBCH block. Forexample, the SS/PBCH block may indicate that it has been transmitted inaccordance with a transmission pattern, wherein a SS/PBCH block in thetransmission pattern is a known distance from the frame boundary.

The PBCH may use a QPSK modulation and may use forward error correction(FEC). The FEC may use polar coding. One or more symbols spanned by thePBCH may carry one or more DMRSs for demodulation of the PBCH. The PBCHmay include an indication of a current system frame number (SFN) of thecell and/or a SS/PBCH block timing index. These parameters mayfacilitate time synchronization of the UE to the base station. The PBCHmay include a master information block (MIB) used to provide the UE withone or more parameters. The MIB may be used by the UE to locateremaining minimum system information (RMSI) associated with the cell.The RMSI may include a System Information Block Type 1 (SIB1). The SIB1may contain information needed by the UE to access the cell. The UE mayuse one or more parameters of the MIB to monitor PDCCH, which may beused to schedule PDSCH. The PDSCH may include the SIB1. The SIB1 may bedecoded using parameters provided in the MIB. The PBCH may indicate anabsence of SIB1. Based on the PBCH indicating the absence of SIB1, theUE may be pointed to a frequency. The UE may search for an SS/PBCH blockat the frequency to which the UE is pointed.

The UE may assume that one or more SS/PBCH blocks transmitted with asame SS/PBCH block index are quasi co-located (QCLed) (e.g., having thesame/similar Doppler spread, Doppler shift, average gain, average delay,and/or spatial Rx parameters). The UE may not assume QCL for SS/PBCHblock transmissions having different SS/PBCH block indices.

SS/PBCH blocks (e.g., those within a half-frame) may be transmitted inspatial directions (e.g., using different beams that span a coveragearea of the cell). In an example, a first SS/PBCH block may betransmitted in a first spatial direction using a first beam, and asecond SS/PBCH block may be transmitted in a second spatial directionusing a second beam.

In an example, within a frequency span of a carrier, a base station maytransmit a plurality of SS/PBCH blocks. In an example, a first PCI of afirst SS/PBCH block of the plurality of SS/PBCH blocks may be differentfrom a second PCI of a second SS/PBCH block of the plurality of SS/PBCHblocks. The PCIs of SS/PBCH blocks transmitted in different frequencylocations may be different or the same.

The CSI-RS may be transmitted by the base station and used by the UE toacquire channel state information (CSI). The base station may configurethe UE with one or more CSI-RSs for channel estimation or any othersuitable purpose. The base station may configure a UE with one or moreof the same/similar CSI-RSs. The UE may measure the one or more CSI-RSs.The UE may estimate a downlink channel state and/or generate a CSIreport based on the measuring of the one or more downlink CSI-RSs. TheUE may provide the CSI report to the base station. The base station mayuse feedback provided by the UE (e.g., the estimated downlink channelstate) to perform link adaptation.

The base station may semi-statically configure the UE with one or moreCSI-RS resource sets. A CSI-RS resource may be associated with alocation in the time and frequency domains and a periodicity. The basestation may selectively activate and/or deactivate a CSI-RS resource.The base station may indicate to the UE that a CSI-RS resource in theCSI-RS resource set is activated and/or deactivated.

The base station may configure the UE to report CSI measurements. Thebase station may configure the UE to provide CSI reports periodically,aperiodically, or semi-persistently. For periodic CSI reporting, the UEmay be configured with a timing and/or periodicity of a plurality of CSIreports. For aperiodic CSI reporting, the base station may request a CSIreport. For example, the base station may command the UE to measure aconfigured CSI-RS resource and provide a CSI report relating to themeasurements. For semi-persistent CSI reporting, the base station mayconfigure the UE to transmit periodically, and selectively activate ordeactivate the periodic reporting. The base station may configure the UEwith a CSI-RS resource set and CSI reports using RRC signaling.

The CSI-RS configuration may comprise one or more parameters indicating,for example, up to 32 antenna ports. The UE may be configured to employthe same OFDM symbols for a downlink CSI-RS and a control resource set(CORESET) when the downlink CSI-RS and CORESET are spatially QCLed andresource elements associated with the downlink CSI-RS are outside of thephysical resource blocks (PRBs) configured for the CORESET. The UE maybe configured to employ the same OFDM symbols for downlink CSI-RS andSS/PBCH blocks when the downlink CSI-RS and SS/PBCH blocks are spatiallyQCLed and resource elements associated with the downlink CSI-RS areoutside of PRBs configured for the SS/PBCH blocks.

Downlink DMRSs may be transmitted by a base station and used by a UE forchannel estimation. For example, the downlink DMRS may be used forcoherent demodulation of one or more downlink physical channels (e.g.,PDSCH). An NR network may support one or more variable and/orconfigurable DMRS patterns for data demodulation. At least one downlinkDMRS configuration may support a front-loaded DMRS pattern. Afront-loaded DMRS may be mapped over one or more OFDM symbols (e.g., oneor two adjacent OFDM symbols). A base station may semi-staticallyconfigure the UE with a number (e.g. a maximum number) of front-loadedDMRS symbols for PDSCH. A DMRS configuration may support one or moreDMRS ports. For example, for single user-MIMO, a DMRS configuration maysupport up to eight orthogonal downlink DMRS ports per UE. Formultiuser-MIMO, a DMRS configuration may support up to 4 orthogonaldownlink DMRS ports per UE. A radio network may support (e.g., at leastfor CP-OFDM) a common DMRS structure for downlink and uplink, wherein aDMRS location, a DMRS pattern, and/or a scrambling sequence may be thesame or different. The base station may transmit a downlink DMRS and acorresponding PDSCH using the same precoding matrix. The UE may use theone or more downlink DMRSs for coherent demodulation/channel estimationof the PDSCH.

In an example, a transmitter (e.g., a base station) may use a precodermatrices for a part of a transmission bandwidth. For example, thetransmitter may use a first precoder matrix for a first bandwidth and asecond precoder matrix for a second bandwidth. The first precoder matrixand the second precoder matrix may be different based on the firstbandwidth being different from the second bandwidth. The UE may assumethat a same precoding matrix is used across a set of PRBs. The set ofPRBs may be denoted as a precoding resource block group (PRG).

A PDSCH may comprise one or more layers. The UE may assume that at leastone symbol with DMRS is present on a layer of the one or more layers ofthe PDSCH. A higher layer may configure up to 3 DMRSs for the PDSCH.

Downlink PT-RS may be transmitted by a base station and used by a UE forphase-noise compensation. Whether a downlink PT-RS is present or not maydepend on an RRC configuration. The presence and/or pattern of thedownlink PT-RS may be configured on a UE-specific basis using acombination of RRC signaling and/or an association with one or moreparameters employed for other purposes (e.g., modulation and codingscheme (MCS)), which may be indicated by DCI. When configured, a dynamicpresence of a downlink PT-RS may be associated with one or more DCIparameters comprising at least MCS. An NR network may support aplurality of PT-RS densities defined in the time and/or frequencydomains. When present, a frequency domain density may be associated withat least one configuration of a scheduled bandwidth. The UE may assume asame precoding for a DMRS port and a PT-RS port. A number of PT-RS portsmay be fewer than a number of DMRS ports in a scheduled resource.Downlink PT-RS may be confined in the scheduled time/frequency durationfor the UE. Downlink PT-RS may be transmitted on symbols to facilitatephase tracking at the receiver.

The UE may transmit an uplink DMRS to a base station for channelestimation. For example, the base station may use the uplink DMRS forcoherent demodulation of one or more uplink physical channels. Forexample, the UE may transmit an uplink DMRS with a PUSCH and/or a PUCCH.The uplink DM-RS may span a range of frequencies that is similar to arange of frequencies associated with the corresponding physical channel.The base station may configure the UE with one or more uplink DMRSconfigurations. At least one DMRS configuration may support afront-loaded DMRS pattern. The front-loaded DMRS may be mapped over oneor more OFDM symbols (e.g., one or two adjacent OFDM symbols). One ormore uplink DMRSs may be configured to transmit at one or more symbolsof a PUSCH and/or a PUCCH. The base station may semi-staticallyconfigure the UE with a number (e.g. maximum number) of front-loadedDMRS symbols for the PUSCH and/or the PUCCH, which the UE may use toschedule a single-symbol DMRS and/or a double-symbol DMRS. An NR networkmay support (e.g., for cyclic prefix orthogonal frequency divisionmultiplexing (CP-OFDM)) a common DMRS structure for downlink and uplink,wherein a DMRS location, a DMRS pattern, and/or a scrambling sequencefor the DMRS may be the same or different.

A PUSCH may comprise one or more layers, and the UE may transmit atleast one symbol with DMRS present on a layer of the one or more layersof the PUSCH. In an example, a higher layer may configure up to threeDMRSs for the PUSCH.

Uplink PT-RS (which may be used by a base station for phase trackingand/or phase-noise compensation) may or may not be present depending onan RRC configuration of the UE. The presence and/or pattern of uplinkPT-RS may be configured on a UE-specific basis by a combination of RRCsignaling and/or one or more parameters employed for other purposes(e.g., Modulation and Coding Scheme (MCS)), which may be indicated byDCI. When configured, a dynamic presence of uplink PT-RS may beassociated with one or more DCI parameters comprising at least MCS. Aradio network may support a plurality of uplink PT-RS densities definedin time/frequency domain. When present, a frequency domain density maybe associated with at least one configuration of a scheduled bandwidth.The UE may assume a same precoding for a DMRS port and a PT-RS port. Anumber of PT-RS ports may be fewer than a number of DMRS ports in ascheduled resource. For example, uplink PT-RS may be confined in thescheduled time/frequency duration for the UE.

SRS may be transmitted by a UE to a base station for channel stateestimation to support uplink channel dependent scheduling and/or linkadaptation. SRS transmitted by the UE may allow a base station toestimate an uplink channel state at one or more frequencies. A schedulerat the base station may employ the estimated uplink channel state toassign one or more resource blocks for an uplink PUSCH transmission fromthe UE. The base station may semi-statically configure the UE with oneor more SRS resource sets. For an SRS resource set, the base station mayconfigure the UE with one or more SRS resources. An SRS resource setapplicability may be configured by a higher layer (e.g., RRC) parameter.For example, when a higher layer parameter indicates beam management, anSRS resource in a SRS resource set of the one or more SRS resource sets(e.g., with the same/similar time domain behavior, periodic, aperiodic,and/or the like) may be transmitted at a time instant (e.g.,simultaneously). The UE may transmit one or more SRS resources in SRSresource sets. An NR network may support aperiodic, periodic and/orsemi-persistent SRS transmissions. The UE may transmit SRS resourcesbased on one or more trigger types, wherein the one or more triggertypes may comprise higher layer signaling (e.g., RRC) and/or one or moreDCI formats. In an example, at least one DCI format may be employed forthe UE to select at least one of one or more configured SRS resourcesets. An SRS trigger type 0 may refer to an SRS triggered based on ahigher layer signaling. An SRS trigger type 1 may refer to an SRStriggered based on one or more DCI formats. In an example, when PUSCHand SRS are transmitted in a same slot, the UE may be configured totransmit SRS after a transmission of a PUSCH and a corresponding uplinkDMRS.

The base station may semi-statically configure the UE with one or moreSRS configuration parameters indicating at least one of following: a SRSresource configuration identifier; a number of SRS ports; time domainbehavior of an SRS resource configuration (e.g., an indication ofperiodic, semi-persistent, or aperiodic SRS); slot, mini-slot, and/orsubframe level periodicity; offset for a periodic and/or an aperiodicSRS resource; a number of OFDM symbols in an SRS resource; a startingOFDM symbol of an SRS resource; an SRS bandwidth; a frequency hoppingbandwidth; a cyclic shift; and/or an SRS sequence ID.

An antenna port is defined such that the channel over which a symbol onthe antenna port is conveyed can be inferred from the channel over whichanother symbol on the same antenna port is conveyed. If a first symboland a second symbol are transmitted on the same antenna port, thereceiver may infer the channel (e.g., fading gain, multipath delay,and/or the like) for conveying the second symbol on the antenna port,from the channel for conveying the first symbol on the antenna port. Afirst antenna port and a second antenna port may be referred to as quasico-located (QCLed) if one or more large-scale properties of the channelover which a first symbol on the first antenna port is conveyed may beinferred from the channel over which a second symbol on a second antennaport is conveyed. The one or more large-scale properties may comprise atleast one of: a delay spread; a Doppler spread; a Doppler shift; anaverage gain; an average delay; and/or spatial Receiving (Rx)parameters.

Channels that use beamforming require beam management. Beam managementmay comprise beam measurement, beam selection, and beam indication. Abeam may be associated with one or more reference signals. For example,a beam may be identified by one or more beamformed reference signals.The UE may perform downlink beam measurement based on downlink referencesignals (e.g., a channel state information reference signal (CSI-RS))and generate a beam measurement report. The UE may perform the downlinkbeam measurement procedure after an RRC connection is set up with a basestation.

FIG. 11B illustrates an example of channel state information referencesignals (CSI-RSs) that are mapped in the time and frequency domains. Asquare shown in FIG. 11B may span a resource block (RB) within abandwidth of a cell. A base station may transmit one or more RRCmessages comprising CSI-RS resource configuration parameters indicatingone or more CSI-RSs. One or more of the following parameters may beconfigured by higher layer signaling (e.g., RRC and/or MAC signaling)for a CSI-RS resource configuration: a CSI-RS resource configurationidentity, a number of CSI-RS ports, a CSI-RS configuration (e.g., symboland resource element (RE) locations in a subframe), a CSI-RS subframeconfiguration (e.g., subframe location, offset, and periodicity in aradio frame), a CSI-RS power parameter, a CSI-RS sequence parameter, acode division multiplexing (CDM) type parameter, a frequency density, atransmission comb, quasi co-location (QCL) parameters (e.g.,QCL-scramblingidentity, crs-portscount, mbsfn-subframeconfiglist,csi-rs-configZPid, qcl-csi-rs-configNZPid), and/or other radio resourceparameters.

The three beams illustrated in FIG. 11B may be configured for a UE in aUE-specific configuration. Three beams are illustrated in FIG. 11B (beam#1, beam #2, and beam #3), more or fewer beams may be configured. Beam#1 may be allocated with CSI-RS 1101 that may be transmitted in one ormore subcarriers in an RB of a first symbol. Beam #2 may be allocatedwith CSI-RS 1102 that may be transmitted in one or more subcarriers inan RB of a second symbol. Beam #3 may be allocated with CSI-RS 1103 thatmay be transmitted in one or more subcarriers in an RB of a thirdsymbol. By using frequency division multiplexing (FDM), a base stationmay use other subcarriers in a same RB (for example, those that are notused to transmit CSI-RS 1101) to transmit another CSI-RS associated witha beam for another UE. By using time domain multiplexing (TDM), beamsused for the UE may be configured such that beams for the UE use symbolsfrom beams of other UEs.

CSI-RSs such as those illustrated in FIG. 11B (e.g., CSI-RS 1101, 1102,1103) may be transmitted by the base station and used by the UE for oneor more measurements. For example, the UE may measure a reference signalreceived power (RSRP) of configured CSI-RS resources. The base stationmay configure the UE with a reporting configuration and the UE mayreport the RSRP measurements to a network (for example, via one or morebase stations) based on the reporting configuration. In an example, thebase station may determine, based on the reported measurement results,one or more transmission configuration indication (TCI) statescomprising a number of reference signals. In an example, the basestation may indicate one or more TCI states to the UE (e.g., via RRCsignaling, a MAC CE, and/or a DCI). The UE may receive a downlinktransmission with a receive (Rx) beam determined based on the one ormore TCI states. In an example, the UE may or may not have a capabilityof beam correspondence. If the UE has the capability of beamcorrespondence, the UE may determine a spatial domain filter of atransmit (Tx) beam based on a spatial domain filter of the correspondingRx beam. If the UE does not have the capability of beam correspondence,the UE may perform an uplink beam selection procedure to determine thespatial domain filter of the Tx beam. The UE may perform the uplink beamselection procedure based on one or more sounding reference signal (SRS)resources configured to the UE by the base station. The base station mayselect and indicate uplink beams for the UE based on measurements of theone or more SRS resources transmitted by the UE.

In a beam management procedure, a UE may assess (e.g., measure) achannel quality of one or more beam pair links, a beam pair linkcomprising a transmitting beam transmitted by a base station and areceiving beam received by the UE. Based on the assessment, the UE maytransmit a beam measurement report indicating one or more beam pairquality parameters comprising, e.g., one or more beam identifications(e.g., a beam index, a reference signal index, or the like), RSRP, aprecoding matrix indicator (PMI), a channel quality indicator (CQI),and/or a rank indicator (RI).

FIG. 12A illustrates examples of three downlink beam managementprocedures: P1, P2, and P3. Procedure P1 may enable a UE measurement ontransmit (Tx) beams of a transmission reception point (TRP) (or multipleTRPs), e.g., to support a selection of one or more base station Tx beamsand/or UE Rx beams (shown as ovals in the top row and bottom row,respectively, of P1). Beamforming at a TRP may comprise a Tx beam sweepfor a set of beams (shown, in the top rows of P1 and P2, as ovalsrotated in a counter-clockwise direction indicated by the dashed arrow).Beamforming at a UE may comprise an Rx beam sweep for a set of beams(shown, in the bottom rows of P1 and P3, as ovals rotated in a clockwisedirection indicated by the dashed arrow). Procedure P2 may be used toenable a UE measurement on Tx beams of a TRP (shown, in the top row ofP2, as ovals rotated in a counter-clockwise direction indicated by thedashed arrow). The UE and/or the base station may perform procedure P2using a smaller set of beams than is used in procedure P1, or usingnarrower beams than the beams used in procedure P1. This may be referredto as beam refinement. The UE may perform procedure P3 for Rx beamdetermination by using the same Tx beam at the base station and sweepingan Rx beam at the UE.

FIG. 12B illustrates examples of three uplink beam managementprocedures: U1, U2, and U3. Procedure U1 may be used to enable a basestation to perform a measurement on Tx beams of a UE, e.g., to support aselection of one or more UE Tx beams and/or base station Rx beams (shownas ovals in the top row and bottom row, respectively, of U1).Beamforming at the UE may include, e.g., a Tx beam sweep from a set ofbeams (shown in the bottom rows of U1 and U3 as ovals rotated in aclockwise direction indicated by the dashed arrow). Beamforming at thebase station may include, e.g., an Rx beam sweep from a set of beams(shown, in the top rows of U1 and U2, as ovals rotated in acounter-clockwise direction indicated by the dashed arrow). Procedure U2may be used to enable the base station to adjust its Rx beam when the UEuses a fixed Tx beam. The UE and/or the base station may performprocedure U2 using a smaller set of beams than is used in procedure P1,or using narrower beams than the beams used in procedure P1. This may bereferred to as beam refinement The UE may perform procedure U3 to adjustits Tx beam when the base station uses a fixed Rx beam.

A UE may initiate a beam failure recovery (BFR) procedure based ondetecting a beam failure. The UE may transmit a BFR request (e.g., apreamble, a UCI, an SR, a MAC CE, and/or the like) based on theinitiating of the BFR procedure. The UE may detect the beam failurebased on a determination that a quality of beam pair link(s) of anassociated control channel is unsatisfactory (e.g., having an error ratehigher than an error rate threshold, a received signal power lower thana received signal power threshold, an expiration of a timer, and/or thelike).

The UE may measure a quality of a beam pair link using one or morereference signals (RSs) comprising one or more SS/PBCH blocks, one ormore CSI-RS resources, and/or one or more demodulation reference signals(DMRSs). A quality of the beam pair link may be based on one or more ofa block error rate (BLER), an RSRP value, a signal to interference plusnoise ratio (SINR) value, a reference signal received quality (RSRQ)value, and/or a CSI value measured on RS resources. The base station mayindicate that an RS resource is quasi co-located (QCLed) with one ormore DM-RSs of a channel (e.g., a control channel, a shared datachannel, and/or the like). The RS resource and the one or more DMRSs ofthe channel may be QCLed when the channel characteristics (e.g., Dopplershift, Doppler spread, average delay, delay spread, spatial Rxparameter, fading, and/or the like) from a transmission via the RSresource to the UE are similar or the same as the channelcharacteristics from a transmission via the channel to the UE.

A network (e.g., a gNB and/or an ng-eNB of a network) and/or the UE mayinitiate a random access procedure. A UE in an RRC_IDLE state and/or anRRC_INACTIVE state may initiate the random access procedure to request aconnection setup to a network. The UE may initiate the random accessprocedure from an RRC_CONNECTED state. The UE may initiate the randomaccess procedure to request uplink resources (e.g., for uplinktransmission of an SR when there is no PUCCH resource available) and/oracquire uplink timing (e.g., when uplink synchronization status isnon-synchronized). The UE may initiate the random access procedure torequest one or more system information blocks (SIBs) (e.g., other systeminformation such as SIB2, SIB3, and/or the like). The UE may initiatethe random access procedure for a beam failure recovery request. Anetwork may initiate a random access procedure for a handover and/or forestablishing time alignment for an SCell addition.

FIG. 13A illustrates a four-step contention-based random accessprocedure. Prior to initiation of the procedure, a base station maytransmit a configuration message 1310 to the UE. The procedureillustrated in FIG. 13A comprises transmission of four messages: a Msg 11311, a Msg 2 1312, a Msg 3 1313, and a Msg 4 1314. The Msg 1 1311 mayinclude and/or be referred to as a preamble (or a random accesspreamble). The Msg 2 1312 may include and/or be referred to as a randomaccess response (RAR).

The configuration message 1310 may be transmitted, for example, usingone or more RRC messages. The one or more RRC messages may indicate oneor more random access channel (RACH) parameters to the UE. The one ormore RACH parameters may comprise at least one of following: generalparameters for one or more random access procedures (e.g.,RACH-configGeneral); cell-specific parameters (e.g., RACH-ConfigCommon);and/or dedicated parameters (e.g., RACH-configDedicated). The basestation may broadcast or multicast the one or more RRC messages to oneor more UEs. The one or more RRC messages may be UE-specific (e.g.,dedicated RRC messages transmitted to a UE in an RRC_CONNECTED stateand/or in an RRC_INACTIVE state). The UE may determine, based on the oneor more RACH parameters, a time-frequency resource and/or an uplinktransmit power for transmission of the Msg 1 1311 and/or the Msg 3 1313.Based on the one or more RACH parameters, the UE may determine areception timing and a downlink channel for receiving the Msg 2 1312 andthe Msg 4 1314.

The one or more RACH parameters provided in the configuration message1310 may indicate one or more Physical RACH (PRACH) occasions availablefor transmission of the Msg 1 1311. The one or more PRACH occasions maybe predefined. The one or more RACH parameters may indicate one or moreavailable sets of one or more PRACH occasions (e.g., prach-ConfigIndex).The one or more RACH parameters may indicate an association between (a)one or more PRACH occasions and (b) one or more reference signals. Theone or more RACH parameters may indicate an association between (a) oneor more preambles and (b) one or more reference signals. The one or morereference signals may be SS/PBCH blocks and/or CSI-RSs. For example, theone or more RACH parameters may indicate a number of SS/PBCH blocksmapped to a PRACH occasion and/or a number of preambles mapped to aSS/PBCH blocks.

The one or more RACH parameters provided in the configuration message1310 may be used to determine an uplink transmit power of Msg 1 1311and/or Msg 3 1313. For example, the one or more RACH parameters mayindicate a reference power for a preamble transmission (e.g., a receivedtarget power and/or an initial power of the preamble transmission).There may be one or more power offsets indicated by the one or more RACHparameters. For example, the one or more RACH parameters may indicate: apower ramping step; a power offset between SSB and CSI-RS; a poweroffset between transmissions of the Msg 1 1311 and the Msg 3 1313;and/or a power offset value between preamble groups. The one or moreRACH parameters may indicate one or more thresholds based on which theUE may determine at least one reference signal (e.g., an SSB and/orCSI-RS) and/or an uplink carrier (e.g., a normal uplink (NUL) carrierand/or a supplemental uplink (SUL) carrier).

The Msg 1 1311 may include one or more preamble transmissions (e.g., apreamble transmission and one or more preamble retransmissions). An RRCmessage may be used to configure one or more preamble groups (e.g.,group A and/or group B). A preamble group may comprise one or morepreambles. The UE may determine the preamble group based on a pathlossmeasurement and/or a size of the Msg 3 1313. The UE may measure an RSRPof one or more reference signals (e.g., SSBs and/or CSI-RSs) anddetermine at least one reference signal having an RSRP above an RSRPthreshold (e.g., rsrp-ThresholdSSB and/or rsrp-ThresholdCSI-RS). The UEmay select at least one preamble associated with the one or morereference signals and/or a selected preamble group, for example, if theassociation between the one or more preambles and the at least onereference signal is configured by an RRC message.

The UE may determine the preamble based on the one or more RACHparameters provided in the configuration message 1310. For example, theUE may determine the preamble based on a pathloss measurement, an RSRPmeasurement, and/or a size of the Msg 3 1313. As another example, theone or more RACH parameters may indicate: a preamble format; a maximumnumber of preamble transmissions; and/or one or more thresholds fordetermining one or more preamble groups (e.g., group A and group B). Abase station may use the one or more RACH parameters to configure the UEwith an association between one or more preambles and one or morereference signals (e.g., SSBs and/or CSI-RSs). If the association isconfigured, the UE may determine the preamble to include in Msg 1 1311based on the association. The Msg 1 1311 may be transmitted to the basestation via one or more PRACH occasions. The UE may use one or morereference signals (e.g., SSBs and/or CSI-RS s) for selection of thepreamble and for determining of the PRACH occasion. One or more RACHparameters (e.g., ra-ssb-OccasionMskIndex and/or ra-OccasionList) mayindicate an association between the PRACH occasions and the one or morereference signals.

The UE may perform a preamble retransmission if no response is receivedfollowing a preamble transmission. The UE may increase an uplinktransmit power for the preamble retransmission. The UE may select aninitial preamble transmit power based on a pathloss measurement and/or atarget received preamble power configured by the network. The UE maydetermine to retransmit a preamble and may ramp up the uplink transmitpower. The UE may receive one or more RACH parameters (e.g.,PREAMBLE_POWER_RAMPING_STEP) indicating a ramping step for the preambleretransmission. The ramping step may be an amount of incrementalincrease in uplink transmit power for a retransmission. The UE may rampup the uplink transmit power if the UE determines a reference signal(e.g., SSB and/or CSI-RS) that is the same as a previous preambletransmission. The UE may count a number of preamble transmissions and/orretransmissions (e.g., PREAMBLE_TRANSMISSION_COUNTER). The UE maydetermine that a random access procedure completed unsuccessfully, forexample, if the number of preamble transmissions exceeds a thresholdconfigured by the one or more RACH parameters (e.g., preambleTransMax).

The Msg 2 1312 received by the UE may include an RAR. In some scenarios,the Msg 2 1312 may include multiple RARs corresponding to multiple UEs.The Msg 2 1312 may be received after or in response to the transmittingof the Msg 1 1311. The Msg 2 1312 may be scheduled on the DL-SCH andindicated on a PDCCH using a random access RNTI (RA-RNTI). The Msg 21312 may indicate that the Msg 1 1311 was received by the base station.The Msg 2 1312 may include a time-alignment command that may be used bythe UE to adjust the UE's transmission timing, a scheduling grant fortransmission of the Msg 3 1313, and/or a Temporary Cell RNTI (TC-RNTI).After transmitting a preamble, the UE may start a time window (e.g.,ra-ResponseWindow) to monitor a PDCCH for the Msg 2 1312. The UE maydetermine when to start the time window based on a PRACH occasion thatthe UE uses to transmit the preamble. For example, the UE may start thetime window one or more symbols after a last symbol of the preamble(e.g., at a first PDCCH occasion from an end of a preambletransmission). The one or more symbols may be determined based on anumerology. The PDCCH may be in a common search space (e.g., aType1-PDCCH common search space) configured by an RRC message. The UEmay identify the RAR based on a Radio Network Temporary Identifier(RNTI). RNTIs may be used depending on one or more events initiating therandom access procedure. The UE may use random access RNTI (RA-RNTI).The RA-RNTI may be associated with PRACH occasions in which the UEtransmits a preamble. For example, the UE may determine the RA-RNTIbased on: an OFDM symbol index; a slot index; a frequency domain index;and/or a UL carrier indicator of the PRACH occasions. An example ofRA-RNTI may be as follows:

RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id, where s_id maybe an index of a first OFDM symbol of the PRACH occasion (e.g.,0≤s_id<14), t_id may be an index of a first slot of the PRACH occasionin a system frame (e.g., 0<t_id<80), fid may be an index of the PRACHoccasion in the frequency domain (e.g., 0≤f_id<8), and ul_carrier_id maybe a UL carrier used for a preamble transmission (e.g., 0 for an NULcarrier, and 1 for an SUL carrier).

The UE may transmit the Msg 3 1313 in response to a successful receptionof the Msg 2 1312 (e.g., using resources identified in the Msg 2 1312).The Msg 3 1313 may be used for contention resolution in, for example,the contention-based random access procedure illustrated in FIG. 13A. Insome scenarios, a plurality of UEs may transmit a same preamble to abase station and the base station may provide an RAR that corresponds toa UE. Collisions may occur if the plurality of UEs interpret the RAR ascorresponding to themselves. Contention resolution (e.g., using the Msg3 1313 and the Msg 4 1314) may be used to increase the likelihood thatthe UE does not incorrectly use an identity of another the UE. Toperform contention resolution, the UE may include a device identifier inthe Msg 3 1313 (e.g., a C-RNTI if assigned, a TC-RNTI included in theMsg 2 1312, and/or any other suitable identifier).

The Msg 4 1314 may be received after or in response to the transmittingof the Msg 3 1313. If a C-RNTI was included in the Msg 3 1313, the basestation will address the UE on the PDCCH using the C-RNTI. If the UE'sunique C-RNTI is detected on the PDCCH, the random access procedure isdetermined to be successfully completed. If a TC-RNTI is included in theMsg 3 1313 (e.g., if the UE is in an RRC_IDLE state or not otherwiseconnected to the base station), Msg 4 1314 will be received using aDL-SCH associated with the TC-RNTI. If a MAC PDU is successfully decodedand a MAC PDU comprises the UE contention resolution identity MAC CEthat matches or otherwise corresponds with the CCCH SDU sent (e.g.,transmitted) in Msg 3 1313, the UE may determine that the contentionresolution is successful and/or the UE may determine that the randomaccess procedure is successfully completed.

The UE may be configured with a supplementary uplink (SUL) carrier and anormal uplink (NUL) carrier. An initial access (e.g., random accessprocedure) may be supported in an uplink carrier. For example, a basestation may configure the UE with two separate RACH configurations: onefor an SUL carrier and the other for an NUL carrier. For random accessin a cell configured with an SUL carrier, the network may indicate whichcarrier to use (NUL or SUL). The UE may determine the SUL carrier, forexample, if a measured quality of one or more reference signals is lowerthan a broadcast threshold. Uplink transmissions of the random accessprocedure (e.g., the Msg 1 1311 and/or the Msg 3 1313) may remain on theselected carrier. The UE may switch an uplink carrier during the randomaccess procedure (e.g., between the Msg 1 1311 and the Msg 3 1313) inone or more cases. For example, the UE may determine and/or switch anuplink carrier for the Msg 1 1311 and/or the Msg 3 1313 based on achannel clear assessment (e.g., a listen-before-talk).

FIG. 13B illustrates a two-step contention-free random access procedure.Similar to the four-step contention-based random access procedureillustrated in FIG. 13A, a base station may, prior to initiation of theprocedure, transmit a configuration message 1320 to the UE. Theconfiguration message 1320 may be analogous in some respects to theconfiguration message 1310. The procedure illustrated in FIG. 13Bcomprises transmission of two messages: a Msg 1 1321 and a Msg 2 1322.The Msg 1 1321 and the Msg 2 1322 may be analogous in some respects tothe Msg 1 1311 and a Msg 2 1312 illustrated in FIG. 13A, respectively.As will be understood from FIGS. 13A and 13B, the contention-free randomaccess procedure may not include messages analogous to the Msg 3 1313and/or the Msg 4 1314.

The contention-free random access procedure illustrated in FIG. 13B maybe initiated for a beam failure recovery, other SI request, SCelladdition, and/or handover. For example, a base station may indicate orassign to the UE the preamble to be used for the Msg 1 1321. The UE mayreceive, from the base station via PDCCH and/or RRC, an indication of apreamble (e.g., ra-PreambleIndex).

After transmitting a preamble, the UE may start a time window (e.g.,ra-ResponseWindow) to monitor a PDCCH for the RAR. In the event of abeam failure recovery request, the base station may configure the UEwith a separate time window and/or a separate PDCCH in a search spaceindicated by an RRC message (e.g., recoverySearchSpaceId). The UE maymonitor for a PDCCH transmission addressed to a Cell RNTI (C-RNTI) onthe search space. In the contention-free random access procedureillustrated in FIG. 13B, the UE may determine that a random accessprocedure successfully completes after or in response to transmission ofMsg 1 1321 and reception of a corresponding Msg 2 1322. The UE maydetermine that a random access procedure successfully completes, forexample, if a PDCCH transmission is addressed to a C-RNTI. The UE maydetermine that a random access procedure successfully completes, forexample, if the UE receives an RAR comprising a preamble identifiercorresponding to a preamble transmitted by the UE and/or the RARcomprises a MAC sub-PDU with the preamble identifier. The UE maydetermine the response as an indication of an acknowledgement for an SIrequest.

FIG. 13C illustrates another two-step random access procedure Similar tothe random access procedures illustrated in FIGS. 13A and 13B, a basestation may, prior to initiation of the procedure, transmit aconfiguration message 1330 to the UE. The configuration message 1330 maybe analogous in some respects to the configuration message 1310 and/orthe configuration message 1320. The procedure illustrated in FIG. 13Ccomprises transmission of two messages: a Msg A 1331 and a Msg B 1332.

Msg A 1331 may be transmitted in an uplink transmission by the UE. Msg A1331 may comprise one or more transmissions of a preamble 1341 and/orone or more transmissions of a transport block 1342. The transport block1342 may comprise contents that are similar and/or equivalent to thecontents of the Msg 3 1313 illustrated in FIG. 13A. The transport block1342 may comprise UCI (e.g., an SR, a HARQ ACK/NACK, and/or the like).The UE may receive the Msg B 1332 after or in response to transmittingthe Msg A 1331. The Msg B 1332 may comprise contents that are similarand/or equivalent to the contents of the Msg 2 1312 (e.g., an RAR)illustrated in FIGS. 13A and 13B and/or the Msg 4 1314 illustrated inFIG. 13A.

The UE may initiate the two-step random access procedure in FIG. 13C forlicensed spectrum and/or unlicensed spectrum. The UE may determine,based on one or more factors, whether to initiate the two-step randomaccess procedure. The one or more factors may be: a radio accesstechnology in use (e.g., LTE, NR, and/or the like); whether the UE hasvalid TA or not; a cell size; the UE's RRC state; a type of spectrum(e.g., licensed vs. unlicensed); and/or any other suitable factors.

The UE may determine, based on two-step RACH parameters included in theconfiguration message 1330, a radio resource and/or an uplink transmitpower for the preamble 1341 and/or the transport block 1342 included inthe Msg A 1331. The RACH parameters may indicate a modulation and codingschemes (MCS), a time-frequency resource, and/or a power control for thepreamble 1341 and/or the transport block 1342. A time-frequency resourcefor transmission of the preamble 1341 (e.g., a PRACH) and atime-frequency resource for transmission of the transport block 1342(e.g., a PUSCH) may be multiplexed using FDM, TDM, and/or CDM. The RACHparameters may enable the UE to determine a reception timing and adownlink channel for monitoring for and/or receiving Msg B 1332.

The transport block 1342 may comprise data (e.g., delay-sensitive data),an identifier of the UE, security information, and/or device information(e.g., an International Mobile Subscriber Identity (IMSI)). The basestation may transmit the Msg B 1332 as a response to the Msg A 1331. TheMsg B 1332 may comprise at least one of following: a preambleidentifier; a timing advance command; a power control command; an uplinkgrant (e.g., a radio resource assignment and/or an MCS); a UE identifierfor contention resolution; and/or an RNTI (e.g., a C-RNTI or a TC-RNTI).The UE may determine that the two-step random access procedure issuccessfully completed if: a preamble identifier in the Msg B 1332 ismatched to a preamble transmitted by the UE; and/or the identifier ofthe UE in Msg B 1332 is matched to the identifier of the UE in the Msg A1331 (e.g., the transport block 1342).

A UE and a base station may exchange control signaling. The controlsignaling may be referred to as L1/L2 control signaling and mayoriginate from the PHY layer (e.g., layer 1) and/or the MAC layer (e.g.,layer 2). The control signaling may comprise downlink control signalingtransmitted from the base station to the UE and/or uplink controlsignaling transmitted from the UE to the base station.

The downlink control signaling may comprise: a downlink schedulingassignment; an uplink scheduling grant indicating uplink radio resourcesand/or a transport format; a slot format information; a preemptionindication; a power control command; and/or any other suitablesignaling. The UE may receive the downlink control signaling in apayload transmitted by the base station on a physical downlink controlchannel (PDCCH). The payload transmitted on the PDCCH may be referred toas downlink control information (DCI). In some scenarios, the PDCCH maybe a group common PDCCH (GC-PDCCH) that is common to a group of UEs.

A base station may attach one or more cyclic redundancy check (CRC)parity bits to a DCI in order to facilitate detection of transmissionerrors. When the DCI is intended for a UE (or a group of the UEs), thebase station may scramble the CRC parity bits with an identifier of theUE (or an identifier of the group of the UEs). Scrambling the CRC paritybits with the identifier may comprise Modulo-2 addition (or an exclusiveOR operation) of the identifier value and the CRC parity bits. Theidentifier may comprise a 16-bit value of a radio network temporaryidentifier (RNTI).

DCIs may be used for different purposes. A purpose may be indicated bythe type of RNTI used to scramble the CRC parity bits. For example, aDCI having CRC parity bits scrambled with a paging RNTI (P-RNTI) mayindicate paging information and/or a system information changenotification. The P-RNTI may be predefined as “FFFE” in hexadecimal. ADCI having CRC parity bits scrambled with a system information RNTI(SI-RNTI) may indicate a broadcast transmission of the systeminformation. The SI-RNTI may be predefined as “FFFF” in hexadecimal. ADCI having CRC parity bits scrambled with a random access RNTI (RA-RNTI)may indicate a random access response (RAR). A DCI having CRC paritybits scrambled with a cell RNTI (C-RNTI) may indicate a dynamicallyscheduled unicast transmission and/or a triggering of PDCCH-orderedrandom access. A DCI having CRC parity bits scrambled with a temporarycell RNTI (TC-RNTI) may indicate a contention resolution (e.g., a Msg 3analogous to the Msg 3 1313 illustrated in FIG. 13A). Other RNTIsconfigured to the UE by a base station may comprise a ConfiguredScheduling RNTI (CS-RNTI), a Transmit Power Control-PUCCH RNTI(TPC-PUCCH-RNTI), a Transmit Power Control-PUSCH RNTI (TPC-PUSCH-RNTI),a Transmit Power Control-SRS RNTI (TPC-SRS-RNTI), an Interruption RNTI(INT-RNTI), a Slot Format Indication RNTI (SFI-RNTI), a Semi-PersistentCSI RNTI (SP-CSI-RNTI), a Modulation and Coding Scheme Cell RNTI(MCS-C-RNTI), and/or the like.

Depending on the purpose and/or content of a DCI, the base station maytransmit the DCIs with one or more DCI formats. For example, DCI format0_0 may be used for scheduling of PUSCH in a cell. DCI format 0_0 may bea fallback DCI format (e.g., with compact DCI payloads). DCI format 0_1may be used for scheduling of PUSCH in a cell (e.g., with more DCIpayloads than DCI format 0_0). DCI format 1_0 may be used for schedulingof PDSCH in a cell. DCI format 1_0 may be a fallback DCI format (e.g.,with compact DCI payloads). DCI format 1_1 may be used for scheduling ofPDSCH in a cell (e.g., with more DCI payloads than DCI format 1_0). DCIformat 2_0 may be used for providing a slot format indication to a groupof UEs. DCI format 2_1 may be used for notifying a group of UEs of aphysical resource block and/or OFDM symbol where the UE may assume notransmission is intended to the UE. DCI format 2_2 may be used fortransmission of a transmit power control (TPC) command for PUCCH orPUSCH. DCI format 2_3 may be used for transmission of a group of TPCcommands for SRS transmissions by one or more UEs. DCI format(s) for newfunctions may be defined in future releases. DCI formats may havedifferent DCI sizes, or may share the same DCI size.

After scrambling a DCI with a RNTI, the base station may process the DCIwith channel coding (e.g., polar coding), rate matching, scramblingand/or QPSK modulation. A base station may map the coded and modulatedDCI on resource elements used and/or configured for a PDCCH. Based on apayload size of the DCI and/or a coverage of the base station, the basestation may transmit the DCI via a PDCCH occupying a number ofcontiguous control channel elements (CCEs). The number of the contiguousCCEs (referred to as aggregation level) may be 1, 2, 4, 8, 16, and/orany other suitable number. A CCE may comprise a number (e.g., 6) ofresource-element groups (REGs). A REG may comprise a resource block inan OFDM symbol. The mapping of the coded and modulated DCI on theresource elements may be based on mapping of CCEs and REGs (e.g.,CCE-to-REG mapping).

FIG. 14A illustrates an example of CORESET configurations for abandwidth part. The base station may transmit a DCI via a PDCCH on oneor more control resource sets (CORESETs). A CORESET may comprise atime-frequency resource in which the UE tries to decode a DCI using oneor more search spaces. The base station may configure a CORESET in thetime-frequency domain. In the example of FIG. 14A, a first CORESET 1401and a second CORESET 1402 occur at the first symbol in a slot. The firstCORESET 1401 overlaps with the second CORESET 1402 in the frequencydomain. A third CORESET 1403 occurs at a third symbol in the slot. Afourth CORESET 1404 occurs at the seventh symbol in the slot. CORESETsmay have a different number of resource blocks in frequency domain.

FIG. 14B illustrates an example of a CCE-to-REG mapping for DCItransmission on a CORESET and PDCCH processing. The CCE-to-REG mappingmay be an interleaved mapping (e.g., for the purpose of providingfrequency diversity) or a non-interleaved mapping (e.g., for thepurposes of facilitating interference coordination and/orfrequency-selective transmission of control channels). The base stationmay perform different or same CCE-to-REG mapping on different CORESETs.A CORESET may be associated with a CCE-to-REG mapping by RRCconfiguration. A CORESET may be configured with an antenna port quasico-location (QCL) parameter. The antenna port QCL parameter may indicateQCL information of a demodulation reference signal (DMRS) for PDCCHreception in the CORESET.

The base station may transmit, to the UE, RRC messages comprisingconfiguration parameters of one or more CORESETs and one or more searchspace sets. The configuration parameters may indicate an associationbetween a search space set and a CORESET. A search space set maycomprise a set of PDCCH candidates formed by CCEs at a given aggregationlevel. The configuration parameters may indicate: a number of PDCCHcandidates to be monitored per aggregation level; a PDCCH monitoringperiodicity and a PDCCH monitoring pattern; one or more DCI formats tobe monitored by the UE; and/or whether a search space set is a commonsearch space set or a UE-specific search space set. A set of CCEs in thecommon search space set may be predefined and known to the UE. A set ofCCEs in the UE-specific search space set may be configured based on theUE's identity (e.g., C-RNTI).

As shown in FIG. 14B, the UE may determine a time-frequency resource fora CORESET based on RRC messages. The UE may determine a CCE-to-REGmapping (e.g., interleaved or non-interleaved, and/or mappingparameters) for the CORESET based on configuration parameters of theCORESET. The UE may determine a number (e.g., at most 10) of searchspace sets configured on the CORESET based on the RRC messages. The UEmay monitor a set of PDCCH candidates according to configurationparameters of a search space set. The UE may monitor a set of PDCCHcandidates in one or more CORESETs for detecting one or more DCIs.Monitoring may comprise decoding one or more PDCCH candidates of the setof the PDCCH candidates according to the monitored DCI formats.Monitoring may comprise decoding a DCI content of one or more PDCCHcandidates with possible (or configured) PDCCH locations, possible (orconfigured) PDCCH formats (e.g., number of CCEs, number of PDCCHcandidates in common search spaces, and/or number of PDCCH candidates inthe UE-specific search spaces) and possible (or configured) DCI formats.The decoding may be referred to as blind decoding. The UE may determinea DCI as valid for the UE, in response to CRC checking (e.g., scrambledbits for CRC parity bits of the DCI matching a RNTI value). The UE mayprocess information contained in the DCI (e.g., a scheduling assignment,an uplink grant, power control, a slot format indication, a downlinkpreemption, and/or the like).

The UE may transmit uplink control signaling (e.g., uplink controlinformation (UCI)) to a base station. The uplink control signaling maycomprise hybrid automatic repeat request (HARQ) acknowledgements forreceived DL-SCH transport blocks. The UE may transmit the HARQacknowledgements after receiving a DL-SCH transport block. Uplinkcontrol signaling may comprise channel state information (CSI)indicating channel quality of a physical downlink channel. The UE maytransmit the CSI to the base station. The base station, based on thereceived CSI, may determine transmission format parameters (e.g.,comprising multi-antenna and beamforming schemes) for a downlinktransmission. Uplink control signaling may comprise scheduling requests(SR). The UE may transmit an SR indicating that uplink data is availablefor transmission to the base station. The UE may transmit a UCI (e.g.,HARQ acknowledgements (HARQ-ACK), CSI report, SR, and the like) via aphysical uplink control channel (PUCCH) or a physical uplink sharedchannel (PUSCH). The UE may transmit the uplink control signaling via aPUCCH using one of several PUCCH formats.

There may be five PUCCH formats and the UE may determine a PUCCH formatbased on a size of the UCI (e.g., a number of uplink symbols of UCItransmission and a number of UCI bits). PUCCH format 0 may have a lengthof one or two OFDM symbols and may include two or fewer bits. The UE maytransmit UCI in a PUCCH resource using PUCCH format 0 if thetransmission is over one or two symbols and the number of HARQ-ACKinformation bits with positive or negative SR (HARQ-ACK/SR bits) is oneor two. PUCCH format 1 may occupy a number between four and fourteenOFDM symbols and may include two or fewer bits. The UE may use PUCCHformat 1 if the transmission is four or more symbols and the number ofHARQ-ACK/SR bits is one or two. PUCCH format 2 may occupy one or twoOFDM symbols and may include more than two bits. The UE may use PUCCHformat 2 if the transmission is over one or two symbols and the numberof UCI bits is two or more. PUCCH format 3 may occupy a number betweenfour and fourteen OFDM symbols and may include more than two bits. TheUE may use PUCCH format 3 if the transmission is four or more symbols,the number of UCI bits is two or more and PUCCH resource does notinclude an orthogonal cover code. PUCCH format 4 may occupy a numberbetween four and fourteen OFDM symbols and may include more than twobits. The UE may use PUCCH format 4 if the transmission is four or moresymbols, the number of UCI bits is two or more and the PUCCH resourceincludes an orthogonal cover code.

The base station may transmit configuration parameters to the UE for aplurality of PUCCH resource sets using, for example, an RRC message. Theplurality of PUCCH resource sets (e.g., up to four sets) may beconfigured on an uplink BWP of a cell. A PUCCH resource set may beconfigured with a PUCCH resource set index, a plurality of PUCCHresources with a PUCCH resource being identified by a PUCCH resourceidentifier (e.g., pucch-Resourceid), and/or a number (e.g. a maximumnumber) of UCI information bits the UE may transmit using one of theplurality of PUCCH resources in the PUCCH resource set. When configuredwith a plurality of PUCCH resource sets, the UE may select one of theplurality of PUCCH resource sets based on a total bit length of the UCIinformation bits (e.g., HARQ-ACK, SR, and/or CSI). If the total bitlength of UCI information bits is two or fewer, the UE may select afirst PUCCH resource set having a PUCCH resource set index equal to “0”.If the total bit length of UCI information bits is greater than two andless than or equal to a first configured value, the UE may select asecond PUCCH resource set having a PUCCH resource set index equal to“1”. If the total bit length of UCI information bits is greater than thefirst configured value and less than or equal to a second configuredvalue, the UE may select a third PUCCH resource set having a PUCCHresource set index equal to “2”. If the total bit length of UCIinformation bits is greater than the second configured value and lessthan or equal to a third value (e.g., 1406), the UE may select a fourthPUCCH resource set having a PUCCH resource set index equal to “3”.

After determining a PUCCH resource set from a plurality of PUCCHresource sets, the UE may determine a PUCCH resource from the PUCCHresource set for UCI (HARQ-ACK, CSI, and/or SR) transmission. The UE maydetermine the PUCCH resource based on a PUCCH resource indicator in aDCI (e.g., with a DCI format 1_0 or DCI for 1_1) received on a PDCCH. Athree-bit PUCCH resource indicator in the DCI may indicate one of eightPUCCH resources in the PUCCH resource set. Based on the PUCCH resourceindicator, the UE may transmit the UCI (HARQ-ACK, CSI and/or SR) using aPUCCH resource indicated by the PUCCH resource indicator in the DCI.

FIG. 15 illustrates an example of a wireless device 1502 incommunication with a base station 1504 in accordance with embodiments ofthe present disclosure. The wireless device 1502 and base station 1504may be part of a mobile communication network, such as the mobilecommunication network 100 illustrated in FIG. 1A, the mobilecommunication network 150 illustrated in FIG. 1B, or any othercommunication network. Only one wireless device 1502 and one basestation 1504 are illustrated in FIG. 15 , but it will be understood thata mobile communication network may include more than one UE and/or morethan one base station, with the same or similar configuration as thoseshown in FIG. 15 .

The base station 1504 may connect the wireless device 1502 to a corenetwork (not shown) through radio communications over the air interface(or radio interface) 1506. The communication direction from the basestation 1504 to the wireless device 1502 over the air interface 1506 isknown as the downlink, and the communication direction from the wirelessdevice 1502 to the base station 1504 over the air interface is known asthe uplink. Downlink transmissions may be separated from uplinktransmissions using FDD, TDD, and/or some combination of the twoduplexing techniques.

In the downlink, data to be sent to the wireless device 1502 from thebase station 1504 may be provided to the processing system 1508 of thebase station 1504. The data may be provided to the processing system1508 by, for example, a core network. In the uplink, data to be sent tothe base station 1504 from the wireless device 1502 may be provided tothe processing system 1518 of the wireless device 1502. The processingsystem 1508 and the processing system 1518 may implement layer 3 andlayer 2 OSI functionality to process the data for transmission. Layer 2may include an SDAP layer, a PDCP layer, an RLC layer, and a MAC layer,for example, with respect to FIG. 2A, FIG. 2B, FIG. 3 , and FIG. 4A.Layer 3 may include an RRC layer as with respect to FIG. 2B.

After being processed by processing system 1508, the data to be sent tothe wireless device 1502 may be provided to a transmission processingsystem 1510 of base station 1504. Similarly, after being processed bythe processing system 1518, the data to be sent to base station 1504 maybe provided to a transmission processing system 1520 of the wirelessdevice 1502. The transmission processing system 1510 and thetransmission processing system 1520 may implement layer 1 OSIfunctionality. Layer 1 may include a PHY layer with respect to FIG. 2A,FIG. 2B, FIG. 3 , and FIG. 4A. For transmit processing, the PHY layermay perform, for example, forward error correction coding of transportchannels, interleaving, rate matching, mapping of transport channels tophysical channels, modulation of physical channel, multiple-inputmultiple-output (MIMO) or multi-antenna processing, and/or the like.

At the base station 1504, a reception processing system 1512 may receivethe uplink transmission from the wireless device 1502. At the wirelessdevice 1502, a reception processing system 1522 may receive the downlinktransmission from base station 1504. The reception processing system1512 and the reception processing system 1522 may implement layer 1 OSIfunctionality. Layer 1 may include a PHY layer with respect to FIG. 2A,FIG. 2B, FIG. 3 , and FIG. 4A. For receive processing, the PHY layer mayperform, for example, error detection, forward error correctiondecoding, deinterleaving, demapping of transport channels to physicalchannels, demodulation of physical channels, MIMO or multi-antennaprocessing, and/or the like.

As shown in FIG. 15 , a wireless device 1502 and the base station 1504may include multiple antennas. The multiple antennas may be used toperform one or more MIMO or multi-antenna techniques, such as spatialmultiplexing (e.g., single-user MIMO or multi-user MIMO),transmit/receive diversity, and/or beamforming. In other examples, thewireless device 1502 and/or the base station 1504 may have a singleantenna.

The processing system 1508 and the processing system 1518 may beassociated with a memory 1514 and a memory 1524, respectively. Memory1514 and memory 1524 (e.g., one or more non-transitory computer readablemediums) may store computer program instructions or code that may beexecuted by the processing system 1508 and/or the processing system 1518to carry out one or more of the functionalities discussed in the presentapplication. Although not shown in FIG. 15 , the transmission processingsystem 1510, the transmission processing system 1520, the receptionprocessing system 1512, and/or the reception processing system 1522 maybe coupled to a memory (e.g., one or more non-transitory computerreadable mediums) storing computer program instructions or code that maybe executed to carry out one or more of their respectivefunctionalities.

The processing system 1508 and/or the processing system 1518 maycomprise one or more controllers and/or one or more processors. The oneor more controllers and/or one or more processors may comprise, forexample, a general-purpose processor, a digital signal processor (DSP),a microcontroller, an application specific integrated circuit (ASIC), afield programmable gate array (FPGA) and/or other programmable logicdevice, discrete gate and/or transistor logic, discrete hardwarecomponents, an on-board unit, or any combination thereof. The processingsystem 1508 and/or the processing system 1518 may perform at least oneof signal coding/processing, data processing, power control,input/output processing, and/or any other functionality that may enablethe wireless device 1502 and the base station 1504 to operate in awireless environment.

The processing system 1508 and/or the processing system 1518 may beconnected to one or more peripherals 1516 and one or more peripherals1526, respectively. The one or more peripherals 1516 and the one or moreperipherals 1526 may include software and/or hardware that providefeatures and/or functionalities, for example, a speaker, a microphone, akeypad, a display, a touchpad, a power source, a satellite transceiver,a universal serial bus (USB) port, a hands-free headset, a frequencymodulated (FM) radio unit, a media player, an Internet browser, anelectronic control unit (e.g., for a motor vehicle), and/or one or moresensors (e.g., an accelerometer, a gyroscope, a temperature sensor, aradar sensor, a lidar sensor, an ultrasonic sensor, a light sensor, acamera, and/or the like). The processing system 1508 and/or theprocessing system 1518 may receive user input data from and/or provideuser output data to the one or more peripherals 1516 and/or the one ormore peripherals 1526. The processing system 1518 in the wireless device1502 may receive power from a power source and/or may be configured todistribute the power to the other components in the wireless device1502. The power source may comprise one or more sources of power, forexample, a battery, a solar cell, a fuel cell, or any combinationthereof. The processing system 1508 and/or the processing system 1518may be connected to a GPS chipset 1517 and a GPS chipset 1527,respectively. The GPS chipset 1517 and the GPS chipset 1527 may beconfigured to provide geographic location information of the wirelessdevice 1502 and the base station 1504, respectively.

FIG. 16A illustrates an example structure for uplink transmission. Abaseband signal representing a physical uplink shared channel mayperform one or more functions. The one or more functions may comprise atleast one of: scrambling; modulation of scrambled bits to generatecomplex-valued symbols; mapping of the complex-valued modulation symbolsonto one or several transmission layers; transform precoding to generatecomplex-valued symbols; precoding of the complex-valued symbols; mappingof precoded complex-valued symbols to resource elements; generation ofcomplex-valued time-domain Single Carrier-Frequency Division MultipleAccess (SC-FDMA) or CP-OFDM signal for an antenna port; and/or the like.In an example, when transform precoding is enabled, a SC-FDMA signal foruplink transmission may be generated. In an example, when transformprecoding is not enabled, an CP-OFDM signal for uplink transmission maybe generated by FIG. 16A. These functions are illustrated as examplesand it is anticipated that other mechanisms may be implemented invarious embodiments.

FIG. 16B illustrates an example structure for modulation andup-conversion of a baseband signal to a carrier frequency. The basebandsignal may be a complex-valued SC-FDMA or CP-OFDM baseband signal for anantenna port and/or a complex-valued Physical Random Access Channel(PRACH) baseband signal. Filtering may be employed prior totransmission.

FIG. 16C illustrates an example structure for downlink transmissions. Abaseband signal representing a physical downlink channel may perform oneor more functions. The one or more functions may comprise: scrambling ofcoded bits in a codeword to be transmitted on a physical channel;modulation of scrambled bits to generate complex-valued modulationsymbols; mapping of the complex-valued modulation symbols onto one orseveral transmission layers; precoding of the complex-valued modulationsymbols on a layer for transmission on the antenna ports; mapping ofcomplex-valued modulation symbols for an antenna port to resourceelements; generation of complex-valued time-domain OFDM signal for anantenna port; and/or the like. These functions are illustrated asexamples and it is anticipated that other mechanisms may be implementedin various embodiments.

FIG. 16D illustrates another example structure for modulation andup-conversion of a baseband signal to a carrier frequency. The basebandsignal may be a complex-valued OFDM baseband signal for an antenna port.Filtering may be employed prior to transmission.

A wireless device may receive from a base station one or more messages(e.g. RRC messages) comprising configuration parameters of a pluralityof cells (e.g. primary cell, secondary cell). The wireless device maycommunicate with at least one base station (e.g. two or more basestations in dual-connectivity) via the plurality of cells. The one ormore messages (e.g. as a part of the configuration parameters) maycomprise parameters of physical, MAC, RLC, PCDP, SDAP, RRC layers forconfiguring the wireless device. For example, the configurationparameters may comprise parameters for configuring physical and MAClayer channels, bearers, etc. For example, the configuration parametersmay comprise parameters indicating values of timers for physical, MAC,RLC, PCDP, SDAP, RRC layers, and/or communication channels.

A timer may begin running once it is started and continue running untilit is stopped or until it expires. A timer may be started if it is notrunning or restarted if it is running. A timer may be associated with avalue (e.g. the timer may be started or restarted from a value or may bestarted from zero and expire once it reaches the value). The duration ofa timer may not be updated until the timer is stopped or expires (e.g.,due to BWP switching). A timer may be used to measure a timeperiod/window for a process. When the specification refers to animplementation and procedure related to one or more timers, it will beunderstood that there are multiple ways to implement the one or moretimers. For example, it will be understood that one or more of themultiple ways to implement a timer may be used to measure a timeperiod/window for the procedure. For example, a random access responsewindow timer may be used for measuring a window of time for receiving arandom access response. In an example, instead of starting and expiry ofa random access response window timer, the time difference between twotime stamps may be used. When a timer is restarted, a process formeasurement of time window may be restarted. Other exampleimplementations may be provided to restart a measurement of a timewindow.

A wireless device may not perform (e.g., may not be allowed to performor may prohibit) an uplink data transmission in an RRC_INACTIVE stateand/or an RRC_IDLE state. In such a case, the wireless device may make(e.g., set up, (re-)establish, and/or resume) a connection to a networkfor transmission(s) of DL (e.g., mobile terminated (MT)) data and/or UL(e.g., mobile originated (MO)) data. For example, a wireless device mayperform one or more procedures (e.g., connection setup procedure) tomake the connection to the network in the RRC_INACTIVE state (or theRRC-IDLE state). For example, the wireless device may perform the one ormore procedures (e.g., connection setup or resume procedure), e.g., whenDL (e.g., mobile terminated (MT)) and/or UL (e.g., mobile originated(MO)) data are available in a buffer. Based on the one or moreprocedures (e.g., in response to successfully completing the connectionsetup or resume procedure), the RRC state of the wireless device maytransition to RRC_CONNECTED state from an RRC_INACTIVE state (or from anRRC_IDLE state). The wireless device may perform a reception of DLtransmission(s) (e.g., receive DL data) and/or UL transmission (e.g.,transmit UL data) in the RRC_CONNECTED state. The wireless device maytransition to the RRC_INACTIVE state (or to the RRC_IDLE state) fromRRC_CONNECTED state, e.g., after or in response to no more DL data(e.g., to be received) and/or UL data (e.g., to be transmitted) inbuffer(s). To transition to the RRC_INACTIVE state from theRRC_CONNECTED state, the wireless device may perform a connectionrelease procedure. The connection release procedure (e.g., an RRCrelease procedure) may result in transitioning the RRC state to theRRC_INACTIVE state (or to the RRC_IDLE) from the RRC_CONNECTED state.

A frequent RRC state transition between an RRC_INACTIVE state (or anRRC_IDLE state) and the RRC_CONNECTED state may require a wirelessdevice to transmit and/or receive a plurality of control signals indifferent layers (e.g., RRC messages, MAC CEs, and/or DCIs). Forexample, for an RRC connection setup, the wireless device may transmit,to a base station, an RRC connection setup request and receive an RRCconnection setup message as a respond to the RRC connection setuprequest. For example, for an RRC connection resume, the wireless devicemay transmit, to a base station, an RRC connection resume request andreceive an RRC connection resume message as a respond to the RRCconnection resume request. For example, for an RRC connection release,the wireless device may receive, from a base station, an RRC connectionrelease request. For example, for DL and/or UL transmission of smalldata available (or arrival) in the RRC_INACTIVE state (or in theRRC_IDLE state), it may be inefficient for a wireless device to make (orresume) an connection to a network (e.g., transition to RRC_CONNECTEDfrom RRC_INACTIVE or RRC_IDLE) and release the connection (e.g.,transition to RRC_INACTIVE or RRC_IDLE from RRC_CONNECTED) after or inresponse to perform the DL and/or UL transmission of small data inRRC_CONNECTED. This may result in increasing unnecessary powerconsumption and/or signaling overhead. For example, the signalingoverhead (e.g., control signaling overhead) required to transmit apayload may be larger than the payload. For example, a frequent RRCstate transition for the small and infrequent DL and/or UL datapacket(s) may cause unnecessary power consumption and signaling overheadfor the wireless device.

Examples of small and infrequent data packets may be such trafficgenerated from smartphone applications, Instant Messaging (IM) services,heart-beat/keep-alive traffic from IM/email clients and other apps, pushnotifications from various applications, non-smartphone applications,wearables (e.g., positioning information), sensors (e.g., fortransmitting temperature, pressure readings periodically or in an eventtriggered manner), and/or smart meters and smart meter networks sendingmeter readings.

A wireless device may perform uplink data transmission(s) in anRRC_INACTIVE state (or in an RRC_IDLE state). For example, a wirelessdevice may transmit one or more data packets in an RRC_INACTIVE state(and/or an RRC_IDLE state). For example, the wireless device mayreceive, from a base station, scheduling information (e.g., RRC message)indicating one or more uplink radio resources in the RRC_INACTIVE statefor the wireless device. The one or more uplink radio resources may befor infrequent data transmission. The one or more uplink radio resourcesmay be for non-periodic data transmission. The one or more uplink radioresources may be for periodic data transmission. The wireless device maytransmit the one or more data packets via the one or more radioresources while keeping its RRC state as the RRC_INACTIVE state (and/orRRC_IDLE state). For example, the wireless device may not transition itsRRC state to the RRC_CONNECTED to transmit the one or more data packetsvia the one or more radio resources. The uplink transmission(s) via theone or more radio resources in an RRC_INACTIVE state (or in an RRC_IDLEstate) may be efficient and flexible (e.g., for low throughput shortdata bursts). The uplink transmission(s) via the one or more radioresources in an RRC_INACTIVE state (or in an RRC_IDLE state) may provideefficient signaling mechanisms (e.g. signaling overhead is less thanpayload). The uplink transmission(s) via the one or more radio resourcesin an RRC_INACTIVE state (or in an RRC_IDLE state) may reduce signalingoverhead. The uplink transmission(s) via the one or more radio resourcesin an RRC_INACTIVE state (or in an RRC_IDLE state) may improve thebattery performance of the wireless device. For example, a wirelessdevice that has intermittent small data packets in the RRC_INACTIVEstate (or the RRC_IDLE state) may benefit from such uplinktransmission(s) in the RRC_INACTIVE state (or the RRC_IDLE state).

In this specification, uplink data transmission(s) in an RRC_INACTIVEstate may be interchangeable with uplink data transmission(s) in anRRC_IDLE state. For example, the procedure(s), configurationparameter(s), and/or feature description(s) that are related to uplinkdata transmission(s) in an RRC_INACTIVE state may be applicable toand/or available to an RRC_IDLE state, e.g., unless specify them for anRRC_IDLE state. In this specification, the procedure(s), configurationparameter(s), and/or feature description(s) that are related to uplinkdata transmission(s) in an RRC_IDLE state may be applicable to and/oravailable to an RRC_INACTIVE state, e.g., unless specify them for anRRC_INACTIVE state. For example, if RRC_CONNECTED and/or RRC_IDLE stateare RRC states that a wireless device has, the procedure(s),configuration parameter(s), and/or feature description(s) that arerelated to uplink data transmission(s) in an RRC_INACTIVE statedescribed in this specification may be applicable to and/or availablefor an RRC_IDLE state of the wireless device. For example, ifRRC_CONNECTED, RRC_INACTIVE, and/or RRC_IDLE state are RRC states that awireless device has, the procedure(s), configuration parameter(s),and/or feature description(s) that are related to uplink datatransmission(s) described in this specification may be applicable toand/or available for an RRC_INACTIVE and/or an RRC_IDLE state of thewireless device.

FIG. 17 is an example of one or more data packet transmission(s) in anRRC_INACTIVE state (or an RRC_IDLE state) as per an aspect of anembodiment of the present disclosure. The one or more data packettransmission(s) in FIG. 17 may be applicable to one or more exampleembodiments in this specification. A wireless device may receive RRCmessage(s) configuring uplink resource(s). The uplink resource(s) may beavailable, scheduled, and/or configured in the RRC_INACTIVE state(and/or RRC_IDLE state). For example, the wireless device may determinewhether to use (and/or initiate, and/or activate) or stop to use (and/orclear, and/or suspend, and/or deactivate) the uplink resource(s) basedon an RRC state of the wireless device. The wireless device may receiveradio resource configuration parameters of one or more uplink radioresources that the wireless device may use in the RRC_INACTIVE state (oran RRC_IDLE state). For example, the one or more uplink radio resourcesmay be (pre-)configured while the wireless device is in theRRC_CONNECTED state, the RRC_INACTIVE state, and/or RRC_IDLE state. Forexample, the wireless device may receive an RRC message comprising theradio resource configuration parameters of the one or more uplink radioresources while the wireless device in the RRC_CONNECTED. The wirelessdevice may not initiate (or activate) the one or more uplink radioresources while the wireless device is in the RRC_CONNECTED state. Forexample, an RRC release message may comprise radio resourceconfiguration parameters of the one or more uplink radio resources. Thewireless device may initiate (or activate) the one or more uplink radioresources after and/or in response to receiving the RRC release message.The wireless device may initiate (and/or activate and/or use) the one ormore uplink radio resources after and/or in response to the RRC state ofthe wireless device being the RRC_INACTIVE state (or an RRC_IDLE state).The wireless device may transmit one or more data packets via the one ormore uplink radio resources while keeping the RRC state as theRRC_INACTIVE state (or an RRC_IDLE state), e.g., without transitioningto the RRC_CONNECTED state). The wireless device may determine totransition the RRC state to the RRC_CONNECTED state from theRRC_INACTIVE state (or an RRC_IDLE state). After or in response totransitioning the RRC state to the RRC_CONNECTED state, the wirelessdevice may determine to stop to use (and/or clear, and/or suspend,and/or deactivate) the one or more uplink resource(s).

In FIG. 17 , a wireless device may determine to transition an RRC stateof the wireless device to an RRC_INACTIVE state (or an RRC_IDLE state)from an RRC_CONNECTED state. The wireless device may determine totransition an RRC state to the RRC_INACTIVE state (or an RRC_IDLE state)after or in response to receiving an RRC message. For example, thewireless device may receive, from a base station, an RRC message (e.g.,RRC release message). The RRC message (e.g., RRC release message) mayindicate a release of an RRC connection from a network. In response toreceiving the RRC message, the wireless device may perform an RRCrelease procedure. The RRC release procedure may comprise a release ofan established radio bearers and/or configured radio resources. The RRCrelease procedure may comprise a suspension of the RRC connection (e.g.,if a signaling radio bearer (SRB) (e.g., SRB2) and/or at least onededicated radio bearer (DRB) are setup) and/or a suspension of theestablished radio bearer(s). After and/or in response to receiving theRRC message (or performing the RRC release procedure), the wirelessdevice may determine to transition an RRC state of the wireless devicesto an RRC_INACTIVE state (or an RRC_IDLE state) from an RRC_CONNECTEDstate.

In FIG. 17 . a wireless device may determine to transition an RRC stateof the wireless device from an RRC_INACTIVE state (or an RRC_IDLE state)to an RRC_CONNECTED state. For example, the wireless device may performa random access procedure to transition to the RRC_CONNECTED state. Thewireless device may perform (and/or initiate) the random accessprocedure for uplink transmission of uplink data, e.g., that arrivesduring the RRC_INACTIVE state (or the RRC_IDLE state). The wirelessdevice may perform the random access procedure after or in response toreceiving a paging message in the RRC_INACTIVE state (or an RRC_IDLEstate). The wireless device may, e.g., periodically, monitor a downlinkcontrol channel for the paging message. The wireless device may receive,from a base station (or a network), the paging message that indicates anidentifier of the wireless device. The paging message may indicate thatthe wireless device performs the random access procedure, e.g., formaking a connection to the network.

A wireless device may receive a message comprising one or moreconfigurations. A configuration of the one or more configuration maycomprise an identifier (or index) of the configuration. each of the oneor more configuration may comprise radio resource configurationparameters of one or more uplink radio resources that the wirelessdevice may use in the RRC_INACTIVE state (or an RRC_IDLE state).

A wireless device may receive an RRC message indicating one or moreuplink radio resources that a wireless device uses in anNon-RRC_CONNECTED state (e.g., RRC_INACTIVE and/or RRC_IDLE). The one ormore uplink radio resources in the Non-RRC_CONNECTED state may be onetime use resource, e.g., for a single transmission. The one or moreuplink radio resources in the Non-RRC_CONNECTED state may be periodicresources, e.g., for one or more uplink transmission(s). The one or moreuplink radio resources in the Non-RRC_CONNECTED state may be referred toas a variety of names in different systems and/or implementations. Theone or more uplink radio resources in the Non-RRC_CONNECTED state may bereferred to as preconfigured uplink resources (PURs). Uplink grantsindicating the one or more uplink radio resources in theNon-RRC_CONNECTED state may be referred to as (pre-)configured grant(s).The (pre-) configured grant(s) may comprise a plurality of types. Forexample, the (pre-)configured grant(s) may comprise a (pre-)configuredgrant Type 1 and/or a (pre-)configured grant Type 2. The one or moreuplink radio resources determined (and/or indicated) by the(pre-)configured grant Type 1 may not require an indication of(re-)initiating (and/or (re-)activating) the one or more uplink radioresources, e.g., after or in response to receiving the RRC messageindicating the one or more uplink radio resources in theNon-RRC_CONNECTED state. For example, the wireless device may(re-)initiate (and/or (re-)activate) the one or more uplink radioresources after or in response to receiving the RRC message comprisingthe (pre-)configured grant Type 1 that indicates the one or more uplinkradio resources in the Non-RRC_CONNECTED state. The one or more uplinkradio resources determined (and/or indicated) by the (pre-)configuredgrant Type 2 may require an indication of (re-)initiating (and/or(re-)activating) the one or more uplink radio resources, e.g., after orin response to receiving the RRC message indicating the one or moreuplink radio resources. For example, the wireless device may not(re-)initiate (and/or (re-)activate) the one or more uplink radioresources after or in response to receiving the RRC message comprisingthe (pre-)configured grant Type 2 that indicates the one or more uplinkradio resources. For example, the wireless device may (re-)initiate(and/or (re-)activate) the one or more uplink radio resources after orin response to receiving the indication of (re-) initiating (and/or(re-)activating) the one or more uplink radio resources in theNon-RRC_CONNECTED state. The wireless device may receive the indicationafter or in response to receiving the RRC message comprising the(pre-)configured grant Type 2 that indicates the one or more uplinkradio resources. The uplink grant(s) indicating the one or more uplinkradio resources in the Non-RRC_CONNECTED state may be referred to as(pre-)configured grant(s) with a particular type indicator, e.g., a(pre-)configured grant type 3, 4, or etc. For example, the(pre-)configured grant Type 1 and the (pre-)configured grant Type 2 mayindicate one or more (periodic) uplink grants in the RRC_CONNECTEDstate. For example, the (pre-)configured grant Type 3 (and/or othertypes of (pre-)configured grant) may indicate one or more (periodic)uplink grants in the Non-RRC_CONNECTED state.

FIG. 18A is an example of (pre-)configured grant(s) indicating one ormore uplink radio resources in a Non-RRC_CONNECTED (e.g., RRC_INACTIVEstate and/or an RRC_IDLE state) as per an aspect of an embodiment of thepresent disclosure. The (pre-)configured grant(s) in FIG. 18A may notrequire an additional activation message (e.g., DCI, MAC CE, and/or RRC)that activates (and/or initiates) the one or more uplink radio resources(and/or (pre-)configured grant(s)). For example, a wireless device mayreceive an RRC message comprising configuration parameters of the(pre-)configured grant(s) of a cell. For example, the RRC message may bean RRC release message. After or in response to receiving the RRCmessage, the wireless device may determine (and/or store) the(pre-)configured grant(s) for the cell. After or in response toreceiving the RRC message, the wireless device may (re-)initiate (oractivate) the (pre-)configured grant. The one or more uplink radioresources (and/or (pre-) configured grant(s)) may be activated and/orinitiated (or valid) in an RRC_INACTIVE state. For example, the wirelessdevice may (re-)initiate (or activate) the (pre-)configured grant tostart in (and/or from) a time reference. For example, the time referencemay be a symbol, a slot, a subframe, an SFN, and/or a hyper-SFN (H-SFN).For example, the H-SFN comprise one or more SFNs (e.g., 1024 SFNs). Forexample, the time reference may be a combination of one or more of asymbol, a slot, a subframe, an SFN, and/or a hyper-SFN (H-SFN). Forexample, the time reference may be a symbol of a slot of an SFN of aH-SFN indicated by the configuration parameters (e.g., a time domainoffset (e.g., indicating the H-SFN, the SFN and/or the slot) and asymbol number S (e.g., indicating the symbol). For example, the wirelessdevice may determine that the (pre-)configured grant (re-)occurs with aperiodicity indicated by the configuration parameters. The wirelessdevice may make a connection to a network (or a base station). Thewireless device may perform an RRC connection setup procedure and/or RRCconnection resume procedure to make the connection. For example, thewireless device may transmit an RRC connection setup request (e.g., forthe RRC connection setup procedure) and/or an RRC connection resumerequest (e.g., for the RRC connection resume procedure). The wirelessdevice may receive, from the base station, a response indicating acomplete of making the RRC connection. For example, the wireless devicemay receive an RRC connection setup complete (e.g., for the RRCconnection setup procedure). For example, the wireless device mayreceive an RRC connection resume complete (e.g., for the RRC connectionresume procedure). In an RRC_CONNECTED state, the one or more uplinkradio resources (and/or (pre-)configured grant(s)) may be deactivatedand/or suspended (cleared, and/or invalid) in an RRC_CONNECTED state.For example, the one or more uplink radio resources (and/or (pre-)configured grant(s)) may be deactivated and/or suspended (cleared,and/or invalid) after or in response to making the connection to thebase station in FIG. 18A (e.g., after or in response to receiving RRCconnection setup and/or resume complete).

FIG. 18B is an example of (pre-)configured grant(s) indicating one ormore uplink radio resources in a Non-RRC_CONNECTED (e.g., RRC_INACTIVEstate and/or an RRC_IDLE state) as per an aspect of an embodiment of thepresent disclosure. The (pre-)configured grant(s) in FIG. 18B mayrequire an additional activation message (e.g., DCI, MAC CE, and/or RRC)that activates (and/or initiates) the one or more uplink radio resources(and/or (pre-) configured grant(s)). For example, a wireless device mayreceive an RRC message comprising configuration parameters of the(pre-)configured grant(s) of a cell. After or in response to receivingthe RRC message, the wireless device may determine (and/or store) the(pre-) configured grant(s) for the cell. For example, the RRC messagemay be an RRC release message. After or in response to receiving the RRCmessage, the wireless device may not (re-) initiate (or activate) the(pre-)configured grant, e.g., until the wireless device receives theadditional activation message (e.g., DCI, MAC CE, and/or RRC). Thewireless device may monitor a PDCCH in the Non-RRC_CONNECTED state toreceive the additional activation message. The wireless device mayreceive the additional activation message (e.g., DCI, MAC CE, and/orRRC) after or in response to receiving the RRC message. A DCI carried bythe PDCCH may be the additional activation message. An MAC CE, and/orRRC message received based on a downlink assignment of a DCI carried bythe PDCCH may be the additional activation message. The configurationparameters in the RRC message may indicate time and frequency resourceallocation of the PDCCH, monitoring occasion(s) of the PDCCH, and/or amonitoring periodicity of the PDCCH. The wireless device may determinethat the (pre-)configured grant (re-)occurs with a periodicity indicatedby the configuration parameters and/or timing offset references (e.g., aH-SFN, a SFN, a slot and/or a symbol). For example, a wireless devicemay determine the SFN (e.g., of the H-SFN), the slot and/or the symbolbased on a reception timing of the additional activation messagereceived via the PDCCH. The wireless device may receive a deactivationmessage that indicates to deactivate and/or suspend (clear, and/orinvalidate) the one or more uplink radio resources (and/or(pre-)configured grant(s)). The wireless device may receive thedeactivation message in the Non-RRC_CONNECTED state. The wireless devicemay make a connection to a network (or a base station). The wirelessdevice may perform a RRC connection setup procedure and/or RRCconnection resume procedure to make the connection. For example, thewireless device may transmit an RRC connection setup request (e.g., forthe RRC connection setup procedure) and/or an RRC connection resumerequest (e.g., for the RRC connection resume procedure). The wirelessdevice may receive, from the base station, a response indicating acomplete of making the RRC connection. For example, the wireless devicemay receive an RRC connection setup complete (e.g., for the RRCconnection setup procedure). For example, the wireless device mayreceive an RRC connection resume complete (e.g., for the RRC connectionresume procedure). After or in response to making the connection to, anRRC state of the wireless device may be transitioned to an RRC_CONNECTEDstate. The one or more uplink radio resources (and/or (pre-)configuredgrant(s)) may be deactivated and/or suspended (cleared, and/or invalid),e.g., after or in response to the RRC state being an RRC_CONNECTEDstate. For example, the one or more uplink radio resources (and/or(pre-)configured grant(s)) may be deactivated and/or suspended (cleared,and/or invalid) after or in response to making the connection to thebase station in FIG. 18B (e.g., after or in response to receiving RRCconnection setup and/or resume complete).

One or more uplink radio resources in an Non-RRC_CONNECTED state may beconfigured by upper layer(s), e.g., RRC layer and/or MAC layer. Forexample, the wireless device may receive, from a base station,message(s) (e.g., RRC message) comprising one or more configurationparameters for transmission of uplink data via the one or more uplinkradio resources in an Non-RRC_CONNECTED state.

In an example, the one or more configuration parameters may indicate anRNTI for transmission(s) of uplink data via the one or more uplink radioresources in an Non-RRC_CONNECTED state. The RNTI may be an identifierof the wireless device. C-RNTI. The RNTI may be C-RNTI. The RNTI may bepreconfigured uplink resource C-RNTI (PUR-C-RNTI or PUR-RNTI). Thewireless device may monitor a PDCCH using the RNTI. For example, thewireless device may monitor the PDCCH using the RNTI after or inresponse to transmission of uplink data via the one or more uplink radioresources. For example, the wireless device may receive, via the PDCCH,DCI with CRC scrambled by the RNTI. The DCI may indicate a positiveacknowledgement of the transmission of the uplink data. The DCI mayindicate a negative acknowledgement of the transmission of the uplinkdata. The DCI may indicate a retransmission of the transmission of theuplink data. The DCI may indicate an uplink grant for theretransmission. The DCI may indicate an updated parameter value(s) ofthe one or more configuration parameters. For example, the DCI mayindicate a (e.g., new or updated) timing advance value for transmissionof uplink data via the one or more uplink radio resources in anNon-RRC_CONNECTED state. The DCI may indicate a trigger of an RAprocedure. The one or more configuration parameters may indicate aduration of a response window (e.g., example parameter name:ResponseWindowSize). The wireless device may monitor the PDCCH for theduration of the response window to receive, from a base station, aresponse (e.g., the DCI) to the transmission of data.

In an example, the one or more configuration parameters may indicate anumber of skipped uplink grants (and/or resource occasions) (e.g.,example parameter name: ImplicitReleaseAfter). Based on the indicatednumber, the wireless device may determine to release (clear, deactivate,discard, and/or suspend) the one or more uplink radio resources, uplinkgrant(s) indicating the one or more uplink radio resources, and/or theone or more configuration parameters. This releasing (clearing,deactivating, discarding, and/or suspending) mechanism may be referredto as an implicit resource release, an implicit preconfigured uplinkresource release, or the like. The number of skipped uplink grants (orresource occasions) indicated by the one or more configurationparameters may be a number of consecutive skipped (and/or empty) uplinkgrants (and/or resource occasions). For example, after or in response toa determination that the wireless device may skip N occasions (e.g., Nconsecutive occasions) of the one or more uplink radio resources or maynot transmit uplink packet(s) via the one or more uplink radio resourcesfor N times (e.g., N=the number of skipped uplink grants and/or resourceoccasions), the wireless device may release (clear, deactivate, discard,and/or suspend) the one or more uplink radio resources, uplink grant(s)indicating the one or more uplink radio resources, and/or the one ormore configuration parameters. The wireless device may not apply (oruse) the implicit resource release (e.g., implicit preconfigured uplinkresource release or the like), e.g., if the one or more configurationparameters does not comprise parameter(s) indicating the number ofskipped uplink grants (and/or resource occasions) (e.g., ifImplicitReleaseAfter is not present in the one or more configurationparameters).

FIG. 19 is an example of one or more data packet transmission(s) in aNon-RRC_CONNECTED (e.g., RRC_INACTIVE and/or an RRC_IDLE) state as peran aspect of an embodiment of the present disclosure. A wireless devicemay receive RRC message(s) configuring uplink resource(s). The uplinkresource(s) may be available, scheduled, and/or configured in theNon-RRC_CONNECTED state. The wireless device may not transmit uplinkpacket(s) one or more occasions of the uplink resource(s). The wirelessdevice may count the one or more occasions. The wireless device maydetermine to release (e.g., may determine to at least one of release,clear, deactivate, and/or suspend) the uplink resource(s), e.g., if anumber of the one or more occasions that the wireless device skip(and/or does not use) to transmit uplink packet(s) is equal to athreshold value. For example, the number of the one or more occasionsmay be a number of consecutive one or more occasions of the uplinkresource(s) that the wireless device skips (and/or does not use).

The wireless device may count a number of skipped uplink grants (and/orresource occasions), e.g., to determine whether to release (clear,deactivate, discard, and/or suspend) the one or more uplink radioresources, uplink grant(s) indicating the one or more uplink radioresources, and/or the one or more configuration parameters. For example,m is the number of skipped uplink grants (and/or resource occasions)that the wireless device counts. The wireless device may determine torelease (clear, deactivate, discard, and/or suspend) the one or moreuplink radio resources, uplink grant(s), and/or the one or moreconfiguration parameters, e.g., if m reaches (e.g., is equal to) athreshold value. The threshold value may be configurable, e.g.,threshold value may be 1, 2, 3, 4, 8, and so on, by the one or moreconfiguration parameters. For example, the one or more configurationparameters may indicate that the threshold value is not configured,e.g., threshold value=disabled. For example, the wireless device maydetermine that the implicit resource release is not applied (e.g., isdisabled), e.g., if the one or more configuration parameters does notcomprise the threshold value.

The wireless device may count a number of skipped uplink grants (and/orresource occasions) with a counter. A value of the counter may bereferred to as m. The counter may be implemented in one or more ways.For example, the value of the counter may increase or decrease based onthe implemented counter. For example, the counter may up-counter thatcounts a number of skipped uplink grants (and/or resource occasions) inincreasing order. In this case, the wireless device may determine torelease (clear, deactivate, discard, and/or suspend) the one or moreuplink radio resources, uplink grant(s) indicating the one or moreuplink radio resources, and/or the one or more configuration parameters,e.g., if the value of counter, m, reaches the threshold value. Forexample, the counter may a down-counter that counts a number of skippeduplink grants (and/or resource occasions) in increasing order in thedecreasing order. In this case, the wireless device may determine torelease (clear, deactivate, discard, and/or suspend) the one or moreuplink radio resources, uplink grant(s) indicating the one or moreuplink radio resources, and/or the one or more configuration parameters,e.g., if the value of counter may start from the threshold value (or afirst predetermined value) and reaches zero (or a second predeterminedvalue). For both counters, the wireless device may determine to release(clear, deactivate, discard, and/or suspend) the one or more uplinkradio resources, uplink grant(s) indicating the one or more uplink radioresources, and/or the one or more configuration parameters, e.g., if anumber of skipped uplink grants (and/or resource occasions) that thewireless device counters reaches the threshold value. In the exampleembodiments in this specification, a mechanism introduced based on theup-counter may be implemented based on the down-counter.

The wireless device may determine to increase m based on at least one offollowings. The wireless device may increase m, e.g., if a radioresource occasion of the one or more uplink radio resource is not used(e.g., the wireless device may increase in if the wireless device doesnot transmit data packet(s) via the radio resource occasion of the oneor more uplink radio resource). The wireless device may increase m,e.g., if a radio resource occasion of the one or more uplink radioresource is not used while the wireless device is in Non-RRC_CONNECTED.The wireless device may increase m, (e.g., uplink grant(s) of the one ormore uplink radio resource and/or resource occasions of the one or moreuplink radio resource skipped), e.g., if no MAC PDU is generated for theuplink grant(s) and/or the resource occasions. The wireless device mayincrease m, e.g., if an radio resource occasion of the one or moreuplink radio resource is used (e.g., the wireless device transmits datapacket(s) via the radio resource occasion of the one or more uplinkradio resource) but no response (e.g., one or more of HARQ ACK, HARQNACK, L2 (e.g., MAC CE) response, and/or L3 (e.g., RRC message)response) corresponding to the data packet(s) is received. The wirelessdevice may increase m, e.g., if the wireless device skips a radioresource occasion of the one or more uplink radio resource due to accessbarring to a cell where the one or more uplink radio resources areconfigured. The wireless device may increase m, e.g., if the wirelessdevice skips a radio resource occasion of the one or more uplink radioresource due to the wireless device being in a wait time (and/orextended wait time). The wait time (and/or extended wait time) maydefines how many seconds the wireless device waits after or in responseto reception of RRC Connection Reject until an RRC connection requestmessage is sent.

A base station (e.g., network) may maintain the counter to be in-syncwith a wireless device. The base station (e.g., network) may determineto increase m based on at least followings. The base station (e.g.,network) may increase m, e.g., if the base station does not receiveuplink packet(s) via a radio resource occasion of the one or more uplinkradio resource. The base station (e.g., network) may increase m, e.g.,while the wireless device is in Non-RRC_CONNECTED. The base station(e.g., network) may increase m, e.g., if the base station (e.g.,network) does not transmit a response (e.g., HARQ feedback (ACK and/orNACK)). For example, the base station (e.g., network) may increase m,e.g., if the base station receives uplink packet(s) via a radio resourceoccasion of the one or more uplink radio resource but does not transmit,to the wireless device, a response to uplink packet(s). For example, theresponse may be an HARQ ACK feedback. For example, the response may bean HARQ NACK feedback. For example, the response may be L2 (e.g., MACCE) response and/or L3 (e.g., RRC message) response. The base station(e.g., network) may increase m, e.g., if a radio resource occasion ofthe one or more uplink radio resource is skipped by the wireless devicedue to access barring to a cell where the one or more uplink radioresources are configured. The base station (e.g., network) may increasem, e.g., if a radio resource occasion of the one or more uplink radioresource is skipped by the wireless device due to the wireless devicebeing in a wait time (and/or extended wait time). The wait time (and/orextended wait time) may defines how many seconds the wireless devicewaits after or in response to reception of RRC Connection Reject untilan RRC connection request message is sent.

The wireless device may determine not to increase m based on at leastone of followings. The wireless device may not increase m, e.g., whilethe wireless device is in an RRC_CONNECTED state. The wireless devicemay not increase m, e.g., after or in response to the one or more uplinkradio resource of the wireless device is suspended (deactivated, and/orcleared). The wireless device may not increase m, e.g., while a barringtimer of the wireless device is running. For example, the wirelessdevice determine, based on the barring timer (e.g., when the barringtimer expires), the time before an access attempt is to be performedafter or in response to an access attempt was barred at access barringcheck. A base station (e.g., network) may maintain the counter to bein-sync with a wireless device. The base station (e.g., network) maydetermine not to increase m based on at least followings. The basestation (e.g., network) may not increase m, e.g., while the wirelessdevice is in an RRC_CONNECTED state. The base station (e.g., network)may not increase m, e.g., after or in response to the one or more uplinkradio resource of the wireless device is suspended (deactivated, and/orcleared). The base station (e.g., network) may not increase m, e.g.,while a barring timer of the wireless device is running. For example,the wireless device determine, based on the barring timer (e.g., whenthe barring timer expires), the time before an access attempt is to beperformed after or in response to an access attempt was barred at accessbarring check.

The wireless device may reset the counter based on at least one offollowings. The wireless device resets (e.g., to zero in the case of theup-counter) after or in response to successful communication between thewireless device and a base station (e.g., network). For example, thewireless device resets (e.g., to zero in the case of the up-counter)after or in response to receiving an ACK corresponding to uplinktransmission via the one or more uplink radio resource. The wirelessdevice may be in an Non-RRC_CONNECTED state. For example, the wirelessdevice resets (e.g., to zero in the case of the up-counter) after or inresponse to transmit an ACK corresponding to a reception of downlinkdata packet(s) from the base station (e.g., network) in theNon-RRC_CONNECTED state. For example, the wireless device may not resetafter or in response to successful communication while the wirelessdevice in the RRC_CONNECTED state. The base station (e.g., network) mayreset the counter based on at least one of followings. The base station(e.g., network) resets (e.g., to zero in the case of the up-counter)after or in response to successful communication between the wirelessdevice and the base station (e.g., network). For example, the basestation (e.g., network) resets (e.g., to zero in the case of theup-counter) after or in response to transmitting an ACK corresponding touplink transmission performed by the wireless device via the one or moreuplink radio resource. The wireless device may perform the uplinktransmission in the Non-RRC_CONNECTED state. For example, the basestation (e.g., network) resets (e.g., to zero in the case of theup-counter) after or in response to receiving, from the wireless device,an ACK corresponding to downlink data packet(s) transmitted to thewireless device while the wireless device in the Non-RRC_CONNECTEDstate. For example, the base station (e.g., network) may not reset afteror in response to successful communication while the wireless device inthe RRC_CONNECTED state.

In an example, the one or more configuration parameters may indicate avalue of a time alignment timer (TAT) (e.g., example parameter name:TimeAlignmentTimer) for a cell (and/or a cell group comprising the cell)where the one or more uplink radio resources in a Non-RRC_CONNECTED(e.g., RRC_INACTIVE and/or RRC_IDLE) state are configured. The cellgroup comprising the cell may be referred to as a timing advance group(TAG). The value of the TAT may indicate how long a timing advanceoffset value is valid and/or is used for adjusting uplink timing foruplink transmission to the cell (and/or cell(s) in the cell group). Forexample, the value of the TAT may determine how long the wireless devicedetermine the cell (and/or cell(s) belonging to the associated TAG) tobe uplink time aligned. The wireless device may determine (or adjust),based on the timing advance offset value, uplink timing for uplinktransmission (e.g., PRACH, PUSCH, SRS, and/or PUCCH transmission) on thecell (and/or cells in the cell group). For example, the timing advanceoffset value may indicate how much (and/or long) the uplink timing foruplink transmission is delayed or advanced for uplink synchronization.For example, the wireless device may run the TAT during a time interval(and/or duration) indicated by the value of the TAT. The wireless devicemay determine that the timing advance offset value is valid (and/or isused) for adjusting uplink timing for uplink transmission on the cell(or cell(s) in the cell group) while the TAT is running. The wirelessdevice may determine that an uplink from the wireless device to the cell(e.g., base station) is out-of-synchronized, e.g., if the TAT associatedwith the cell group (e.g., TAG) to which the cell belongs is not runningand/or expires. For example, the wireless device may stop to performuplink transmission(s) on a cell (and/or cell(s) in the cell group),e.g., if the TAT associated with the cell group (e.g., TAG) to which thecell belongs is not running and/or expires. The wireless device may stopuplink transmissions for a cell, e.g., due to the fact that the (e.g.,maximum) uplink transmission timing difference between TAGs of thewireless device or the (e.g., maximum) uplink transmission timingdifference between TAGs of any MAC entity of the wireless device (e.g.,two MAC entities configured for a dual connectivity) is exceeded, thewireless device may determine the TAT associated with the cell asexpired. The wireless device may perform a random access preamble(re-)transmission and/or MSG A (re-)transmission, e.g., when the TATassociated with the cell group (e.g., TAG) to which the cell belongs isnot running and/or expires. The wireless device may (re-)start the TATafter or in response to receiving a timing advance command thatindicates a (new and/or updated) timing advance offset value of the cell(and/or cells in the cell group). The timing advance command may bereceived as an MAC CE and/or DCI. The timing advance command mayindicate a timing advance offset value of a cell where the one or moreuplink radio resources in a Non-RRC_CONNECTED (e.g., RRC_INACTIVE and/orRRC_IDLE) state.

The wireless device may (re-)start the time alignment timer after or inresponse to transition to a Non-RRC_CONNECTED, e.g., if the wirelessdevice receives (and/or is configured with) the one or more uplink radioresources for the Non-RRC_CONNECTED state. For example, the wirelessdevice may (re-)start the time alignment timer after or in response toreceiving configuration parameter(s) (e.g., timer value of the timealignment timer) associated with the time alignment timer. The wirelessdevice may (re-)start the time alignment timer after or in response toreceiving a timing advance offset value. The wireless device may receivea lower layer control message (e.g., DCI or PDCCH) that indicates thetiming advance offset value. The wireless device may receive an MAClayer control message (e.g., MAC CE and/or RAR) that indicates thetiming advance offset value. For example, the wireless device may(re-)start the time alignment timer after or in response to receiving atiming advance command MAC control element and/or PDCCH indicatingtiming advance adjustment. The wireless device may determine that thetiming advance offset value is valid at least while the TAT is running.The wireless device may validate a TA value based on one or morevalidation conditions. The wireless device may (re-)start the timealignment timer after or in response to a determination that the TA isvalidated. For example, if the TAT has run for a time interval (orduration) indicated by the value of the TAT, the wireless device maydetermine that the TAT expires. The wireless device may determine thatthe timing advance offset value is invalid in response to the expiry ofthe TAT.

Terminologies used in the specification may be interchangeable and/orreferred to as one or more different ones. For example, the timingadvance value may be referred to as a timing alignment value. Forexample, the timing advance offset value may be referred to as a timingalignment offset value. For example, the timing alignment timer may bereferred to as a time alignment timer, a timing advance timer, and/or atime advance timer. For example, the timing advance group may bereferred to as a timing alignment group.

In an example, the one or more configuration parameters may indicate anumber of occasions of the one or more uplink radio resources (e.g., anexample parameter name: NumOccasions). The number of occasions mayindicate that the one or more uplink radio resources is one time useresource (or grant) for a single uplink transmission. The number ofoccasions may indicate that the one or more uplink radio resources is aplurality of uplink radio resources. The number of occasions mayindicate that the one or more uplink radio resources is one or moreperiodic radio resources.

In an example, the one or more configuration parameters may indicate atime domain resource allocation of the one or more uplink radioresources. For example, the one or more configuration parameters mayindicate a periodicity (e.g., example parameter name: Periodicity) ofthe one or more uplink radio resources in the Non-RRC_CONNECTED state.For example, the one or more configuration parameters may comprise atime offset. The time offset may be a time domain offset with respect to(and/or related to) a time reference. The time reference may be aparticular SFN (e.g., of a H-SFN), a particular subframe number, aparticular slot number, a particular symbol number, and/or a combinationthereof. The time reference may be predefined (e.g., SFN=0 and/orH-SFN=0). The time reference may be a predefined value (e.g., SFN=0and/or H-SFN=0), e.g., if a field of the time reference is not presentin the one or more configuration parameters. For example, the wirelessdevice may receive one or more uplink grant(s), e.g., indicated by theone or more configuration parameters. The one or more uplink grant(s)may indicate the one or more uplink radio resources. The one or moreuplink radio resources may start from a symbol (of a slot of an SFN of aH-SFN) indicated by the time offset. The one or more uplink radioresources may occur from the symbol periodically with the periodicity.For example, the wireless device may, e.g., sequentially, determine thatan N^(th) uplink grant of the one or more uplink grant(s) occurs in antransmission time interval (TTI, e.g., slot(s), mini-slot(s), symbol(s))based on the time offset and N*Periodicity. The time offset may bedefined in terms of a number of symbols, a number of slots, a number ofsubframes, a number of SFNs, a number of H-SFNs, and/or a combinationthereof. For example, the one or more configuration parameters maycomprise a parameter, timeDomainOffset or the like. For example,timeDomainOffset indicates the time offset that the wireless devicereceived from a base station. For example, the one or more configurationparameters may comprise a parameter, timeReferenceSFN or the like (e.g.,a time reference reference defined in terms of SFN(s) and/or H-SFN). Forexample, timeReferenceSFN indicates an SFN as the time reference usedfor determination of the time offset of a resource in time domain. Forexample, the SFN may repeat with a period of 1024 frames. For example,the wireless device may receive, via SFN=3, the one or moreconfiguration parameters indicating timeReferenceSFN=0. For example,timeReferenceSFN=0 may indicate a time reference SFN=0 that is 3 SFNsbefore the SFN=3. For example, timeReferenceSFN=0 may indicate a timereference SFN=0 that is 1021 SFNs after the SFN=3. For example, thewireless device may determine the closest SFN with the indicated numberpreceding the reception of the configured grant configuration. Forexample, in the above example, the wireless device may determine thattimeReferenceSFN=0 indicates a time reference SFN=0 that is 3 SFNsbefore the SFN=3. For example, the wireless device may, e.g.,sequentially, determine that the N^(th) uplink grant occurs (and/or theuplink grant recurs) in the symbol for which:RSFN×numberOfSlotsPerFrame×numberOfSymbolsPerSlot)+(slot number in theframe×numberOfSymbolsPerSlot)+symbol number in theslot]=(timeReferenceSFN×numberOfSlotsPerFrame×numberOfSymbolsPerSlot+timeDomainOffset×numberOfSymbolsPerSlot+S+N×periodicity)modulo (1024×numberOfSlotsPerFrame×numberOfSymbolsPerSlot). For example,numberOfSlotsPerFrame is a number of slots in a frame. For example,numberOfSymbolsPerSlot, is a number of symbols in a slot. For example,periodicity is a periodicity of the one or more uplink radio resourcesindicated by the one or more configuration parameters. For example, S isa symbol number (or symbol offset) indicated by the one or moreconfiguration parameters. The determination of the N^(th) uplink grantabove may be a case that (pre-)configured grant(s) in FIG. 18A may notrequire an additional activation message (e.g., DCI, MAC CE, and/or RRC)that activates (and/or initiates) the one or more uplink radio resources(and/or (pre-)configured grant(s)). For example, the wireless devicemay, e.g., sequentially, determine that the N^(th) uplink grant occurs(and/or the uplink grant recurs) in the symbol for which:RSFN×numberOfSlotsPerFrame×numberOfSymbolsPerSlot)+(slot number in theframe×numberOfSymbolsPerSlot)+symbol number in the slot]=[(SFNstarttime×numberOfSlotsPerFrame×numberOfSymbolsPerSlot+slotstarttime×numberOfSymbolsPerSlot+symbolstart time)+N×periodicity] modulo(1024×numberOfSlotsPerFrame×numberOfSymbolsPerSlot). The determinationof the N^(th) uplink grant above may be a case that (pre-)configuredgrant(s) in FIG. 18B may require an additional activation message (e.g.,DCI, MAC CE, and/or RRC) that activates (and/or initiates) the one ormore uplink radio resources (and/or (pre-)configured grant(s)). Forexample, SFNstart time, slotstart time, and symbolstart time are theSFN, slot, and symbol, respectively, at a time the one or more uplinkgrant(s) was (re-)initiated. For example, SFNstart time, slotstart time,and symbolstart time are the SFN, slot, and symbol, respectively, at atime where the wireless device receives an indication (e.g., DCI) of(re-)initiating (and/or (re-)activating) the one or more uplinkgrant(s). For example, SFNstart time, slotstart time, and symbolstarttime are the SFN, slot, and symbol, respectively, of a transmissionopportunity of PUSCH where the one or more uplink grant(s) was(re-)initiated. For example, the transmission opportunity of PUSCH isthe first opportunity of PUSCH where the one or more uplink grant(s) was(re-)initiated.

The wireless device may (re-)initiate transmission via one or moreuplink radio resources in the Non-RRC_CONNECTED state based on one ormore conditions. For example, the wireless device may receiveconfiguration parameter(s) indicating the one or more conditions. Forexample, the wireless device may determine if a cell, where one or moreuplink radio resources in the Non-RRC_CONNECTED state are configured,supports transmission(s) via the one or more uplink radio resources. Forexample, the wireless device may receive RRC message(s) (e.g., SIB). TheRRC message(s) may comprise configuration parameter(s) indicatingwhether the cell supports transmission(s) via the one or more uplinkradio resources. The configuration parameter(s) may indicate which typeof transmission is supported (or available) via the one or more uplinkradio resources. For example, the type may comprise control plane (CP)transmission and/or user-plane (UP) transmission. The configurationparameter(s) may indicate which type of network, the cell is connected,supports the transmission via the one or more uplink radio resources.Depending on the type of network that the cell is connected, thewireless device may determine whether the transmission via the one ormore uplink radio resources is supported in the cell. For example, thetype of network may comprise one or more generations in a network system(e.g., 5G core, Evolved Packet Core (EPC), and/or the like) and/or oneor more wireless technologies (e.g., Wifi, 5G, Bluetooth, and/or thelike). For example, the configuration parameter(s) may indicate whichtype of spectrum (and/or frequency band) supports the transmission viathe one or more uplink radio resources. For example, the type ofspectrum may comprise licensed spectrum and/or unlicensed spectrum. Forexample, the type of spectrum may comprise a CBRS (Citizens BroadbandRadio Service) band (e.g., a wideband in 3.5 GHz band). For example, thetype of spectrum may comprise a millimeter wave band (e.g., over 30 GHzband). The configuration parameter(s) in the RRC message(s) may indicatea combination of the type of network, the type of spectrum, and/or thetype of transmission. For example, parameter(s), cp-PUR-5GC (e.g., theparameter value may be ‘true’/‘false’ or ‘enabled’/‘disabled’), in theRRC message(s) indicate whether CP transmission using PUR is supportedin the cell when connected to 5G core network. For example,parameter(s), cp-PUR-EPC (e.g., the parameter value may be‘true’/‘false’ or ‘enabled’/‘disabled’), in the RRC message(s) indicatewhether CP transmission using PUR is supported in the cell whenconnected to EPC. For example, if the RRC message(s) received from acell indicates cp-PUR-EPC=‘true’ (or ‘enabled’), the wireless devicedetermines that the PUR is supported in the cell when connected to EPC.

The wireless device may (re-)initiate transmission via one or moreuplink radio resources in the Non-RRC_CONNECTED state based on one ormore conditions. For example, the wireless device may (re-)initiatetransmission via one or more uplink radio resources in theNon-RRC_CONNECTED state, e.g., if at least one of following conditionsare satisfied: the wireless device has a valid configuration of the oneor more uplink radio resources; the wireless device has a valid timingadvance value; the wireless device triggers to request establishment ofan RRC connection; the wireless device triggers to request resumption ofan RRC connection; the wireless device has a stored value of a validsecurity parameter (e.g., nextHopChainingCount provided in theRRCConnectionRelease message with suspend indication during thepreceding suspend procedure); the wireless device triggers theestablishment or resumption request for mobile originating calls and/orthe establishment cause is mo-Data or mo-ExceptionData ordelayTolerantAccess; and/or a size of an MAC PDU (e.g., comprising thetotal UL data) is expected to be smaller than or equal to a transportblock size (TBS) configured for PUR.

For example, the wireless device determines, based on one or morevalidation conditions (e.g., a TAT based validation and/or a measurementbased validation), if the wireless device has a valid timing advancevalue. For example, the wireless device may determine the configurationof the one or more uplink radio resources is valid, e.g., based onconfiguration parameter(s) of the one or more uplink radio resourcesindicating a validity of the configuration. For example, the wirelessdevice receives message(s) comprising the configuration parameter(s).the configuration is valid, e.g., if a field, config, in the message(s)is set to setup (e.g., true). For example, the configuration is valid,e.g., if the field, config, is set to release (e.g., false).

The wireless device may determine, based on one or more validationconditions, if a timing advance value is valid or not for transmissionvia the one or more uplink radio resources in the Non-RRC_CONNECTEDstate. For example, the one or more validation conditions may comprise aTAT based validation and/or a measurement based validation. The wirelessdevice may determine to apply the configured condition(s) among the oneor more validation conditions. For example, the wireless device receivesmessage(s) comprising configuration parameters of a first validationcondition (e.g., the TAT based validation) among the one or morevalidation conditions. The message(s) may not comprise configurationparameters of a second validation condition (e.g., the measurement basedvalidation) among the one or more validation conditions. In this case,the wireless device may determine if the timing advance value is validor not at least based on the first validation condition. For example, ifthe message(s) comprising configuration parameters of the firstvalidation condition (e.g., the TAT based validation) and the secondvalidation condition (e.g., the measurement based validation), thewireless device may determine if the timing advance value is valid ornot at least based on the first validation condition and the secondvalidation condition.

For example, for the TAT based validation, the wireless device determinea validity of the timing advance value based on a TAT. The wirelessdevice may receive RRC message(s) comprising a value of the TAT. The TATmay be for a cell (and/or a TAG comprising the cell) where one or moreuplink radio resources in the Non-RRC_CONNECTED state are configured.The wireless device may determine that the timing advance value fortransmission via the one or more uplink radio resources is valid, e.g.,if the TAT is running. The wireless device may determine that thevalidation of the timing advance value for transmission is not at leastbased on the TAT, e.g., if the value of the TAT is not configured (e.g.,the RRC message(s) does not comprise the value of the TAT).

FIG. 20 is an example of one or more data packet transmission(s) in aNon-RRC_CONNECTED (e.g., RRC_INACTIVE and/or an RRC_IDLE) state as peran aspect of an embodiment of the present disclosure. The wirelessdevice may receive RRC message(s) comprising configuration parameters ofuplink resource(s) in the Non-RRC_CONNECTED state. The uplinkresource(s) may be available, scheduled, and/or configured in theNon-RRC_CONNECTED state. The wireless device may transmit uplinkpacket(s) via one of occasions of the uplink resource(s), e.g., if a TAvalue for the transmission is validated. The wireless device maydetermine (e.g., validate) the TA value as valid to be used for one ormore data packet transmission(s) in a Non-RRC_CONNECTED state, e.g., ifa TAT is running. For example, the wireless device may transmit data viauplink resource(s) in a Non-RRC_CONNECTED state, e.g., if the wirelessdevice may determine (e.g., validate) the TA value as valid and/or ifthe TAT is running. For example, if the TAT is not running (and/orexpires), the wireless device may determine that the TA value isinvalid. The wireless device may stop (e.g., is prohibited to perform)uplink transmission via the uplink resource(s).

For example, for the measurement based validation, the wireless devicemay determine, based on measurement(s) of DL RS(s) of a cell where theone or more uplink radio resources are configured. The DL RS(s) may beSSB(s), CSI-RS(s), cell-specific RS(s), and the like. For example, thewireless device may determine, based on the measured value(s) of DLRS(s), if the timing advance value for transmission via the one or moreuplink radio resources is valid. For example, the measured value(s) ofthe DL RS(s) of the cell may be a cell measurement quantity value (e.g.,RSRP, RSRQ, RSSI, and the like). The measured value(s) of the DL RS(s)may be referred to as a serving cell measurement, a measurement quantityof the cell, and/or the like. For example, the wireless device mayreceive RRC message(s) comprising one or more threshold values. Forexample, the wireless device may measure a received signal strength ofat least one DL RS received from the cell (e.g., TRP), e.g., where theone or more uplink radio resources are configured. The at least one DLRS may comprise a synchronization signal (PSS and/or SSS), CSI-RS,and/or cell-specific RS. For example, the measured value of the receivedsignal strength is an RSRP of the at least one DL RS. For example, themeasured value is an RSRQ and/or RSSI (Received Signal StrengthIndicator). The wireless device may determine that the timing advancevalue for transmission via the one or more uplink radio resources isvalid, e.g., if the measured value is within a range indicated by theone or more threshold values. For example, the wireless device maydetermine that the timing advance value for transmission via the one ormore uplink radio resources is valid, e.g., if the measured value hasnot changed more than a range indicated by the one or more thresholdvalues since the wireless device measured a previous DL RS. For example,the wireless device measured the previous DL RS based on measurementconfiguration(s) that schedule one or more measurements, e.g.,independent of resource allocation of the uplink resource(s). Forexample, the wireless device measured the previous DL RS for the last TAvalidation that the wireless device performed for the transmission viathe one or more uplink radio resources.

The one or more threshold values of the measurement comprise an increasethreshold value and/or a decrease threshold value. For example, theincrease threshold value and/or the decrease threshold value mayindicate the threshold value(s) for change in the measured value of theat least one DL RS in the cell. For example, the increase thresholdvalue and/or the decrease threshold value indicates the range that thewireless device determines the TA value as valid (e.g., to be used fortransmission via the one or more uplink radio resources in anNon-RRC_CONNECTED state). For example, the range may indicate a certainarea of the cell (e.g., a certain coverage tier in a cell, e.g., centerarea, cell edge area, etc.), where the TA value is used for transmissionvia the one or more uplink radio resources in the Non-RRC_CONNECTEDstate.

The increase threshold value and/or the decrease threshold value mayindicate value(s) of thresholds in dBm. For example, the wireless devicedetermines the TA value as valid, e.g., if the measurement of DL RS ofthe cell is lower than the increase threshold value. For example, thewireless device determines the TA value as valid, e.g., if themeasurement of DL RS of the cell is higher than or equal to the decreasethreshold value. For example, the wireless device determines the TAvalue as invalid, e.g., if the measurement of DL RS of the cell ishigher than or equal to the increase threshold value, and/or if themeasurement of DL RS of the cell is lower than the decrease thresholdvalue.

FIG. 21A is an example of TA validation as per an aspect of anembodiment of the present disclosure. The wireless device may receivemessage(s) (e.g., RRC message(s)) comprising an increase threshold valueand/or a decrease threshold value. For example, the increase thresholdvalue and/or decrease threshold value may be absolute value(s) ofthreshold(s) (e.g., in dBm). A TA value may be used for transmission inone or more radio resource(s) in a Non-RRC_CONNECTED state, e.g., if themeasurement (e.g., RSRP) is in an RSRP range indicated by the increasethreshold value and/or decrease threshold value. For example, if themeasurement (e.g., RSRP) is less than the increase threshold valueand/or higher than (or equal to) the decrease threshold value, thewireless device may determine that the TA value is valid. For example,if the measurement (e.g., RSRP) is higher than (or equal to) theincrease threshold value and/or lower than the decrease threshold value,the wireless device may determine that the TA value is invalid.

The increase threshold value and/or the decrease threshold value mayindicate value(s), e.g., in dB for the TA validation. For example, thewireless device determines the TA value as valid, e.g., if themeasurement of DL RS of the cell has not increased by more than theincrease threshold value. For example, the wireless device determinesthe TA value as valid, e.g., if the measurement of DL RS of the cell hasnot decreased by more than the decrease threshold value. For example,the wireless device determines the TA value as invalid, e.g., if themeasurement of DL RS of the cell has increased by more than the increasethreshold value, and/or if the measurement of DL RS of the cell hasdecreased by more than the decrease threshold value. The wireless devicemay determine how much the measurement has changed (e.g., has notincreased and/or has not decreased) based on reference measurement(s).For example, the reference measurement(s) are one or more measurementsperformed for the last TA validation. For example, the last TAvalidation may be performed by the wireless device for transmission viathe one or more uplink radio resources in a Non-RRC_CONNECTED state).

FIG. 21B is an example of TA validation as per an aspect of anembodiment of the present disclosure. The wireless device may receivemessage(s) (e.g., RRC message(s)) comprising an increase threshold valueand/or a decrease threshold value. For example, the increase thresholdvalue and/or decrease threshold value may be value(s) of threshold(s)relative to reference measurement(s) (e.g., in dB). For example, whenthe wireless device determines whether a TA value is valid to be usedfor transmission, the wireless device may compare measurement(s) withthe reference measurement(s). For example, the wireless device maydetermine that the TA value is valid, e.g., if the measurement of DL RSof the cell has not increased by more than the increase threshold value,and/or if the measurement of DL RS of the cell has not decreased by morethan the decrease threshold value. Otherwise, the wireless device maydetermine that the TA value is invalid to be used for the transmissionvia the one or more radio resource(s) in a Non-RRC_CONNECTED state.

FIG. 22 is an example geographical view of an increase threshold valueand/or a decrease threshold value as per an aspect of an embodiment ofthe present disclosure. A distance between a cell and a wireless deviceand a measured value of signal strength (e.g., RSRP) of DL RStransmitted from the cell may have an inverse proportionality. Forexample, the greater distance between the cell and the wireless device,the smaller the measured value (e.g., RSRP) of DL RS. For example, ifthe wireless device gets closer to the cell, the measured value may belarger. If the measured value (and/or a change of the measured value) islarger than the increase threshold value, the wireless device maydetermine that the TA value is invalid to be used for transmission. Forexample, if the wireless device moves away from the cell, the measuredvalue may become smaller. If the measured value (and/or a change of themeasured value) of received signal strength is smaller than the decreasethreshold value, the wireless device may determine that the TA value isinvalid to be used for transmission. As shown in FIG. 22 , the wirelessdevice may determine that the TA value is valid, e.g., if the wirelessdevice moves around while keeping the distance from the cell. Forexample, in this case, the measured value (and/or a change of themeasured value) is larger than or equal to the decrease threshold valueand/or smaller than or equal to the increase threshold value.

The wireless device may receive a message comprising the increasethreshold value and decrease threshold value. In this case the wirelessdevice may use the increase threshold value and decrease threshold valuefor the TA validation as disclosed example(s) as per an aspect ofembodiment(s) of the present disclosure. The wireless device may receivea message comprising one of the increase threshold value and/or decreasethreshold value. In this case, the wireless device may use the one ofthe increase threshold value and/or decrease threshold value asdisclosed example(s) as per an aspect of embodiment(s) of the presentdisclosure. For example, the wireless device in a cell edge area mayreceive a message comprising the increase threshold value. For example,the wireless device in a cell center area may receive a messagecomprising the decrease threshold value. The increase threshold valueand decrease threshold value may be absent in the message. For example,the wireless device may receive a message comprising no field value forthe increase threshold value and decrease threshold value. In this case,the wireless device may determine that TA validation is not at leastbased on the measurement(s) (e.g., RSRP, RSRP, and/or RSSI). Forexample, if the increase threshold value and decrease threshold valueare not configured, the TA validation based on change in measurement(s)(e.g., RSRP, RSRP, and/or RSSI) of the cell is not applicable.

After or in response to transmitting data via the one or more uplinkradio resources, the wireless device may monitor PDCCH identified by anRNTI during a response window. For example, the wireless device mayreceive message(s) (e.g., RRC message(s)) indicating the RNTI and/or thesize of the response window (e.g., example parameter name:ResponseWindowTimer). The response window may start from a referencetime associated with transmitting the data via the one or more uplinkradio resources. For example, the reference time may be a transmissiontime interval (e.g., frame, subframe, slot, and/or symbol) where thewireless device transmits the data via the one or more uplink radioresources. For example, the reference time may comprise the end of thecorresponding PUSCH transmission (e.g., the transmission of the data viathe one or more uplink radio resources). For example, the reference timemay be at the first PDCCH occasion from the end of the correspondingPUSCH transmission (e.g., the transmission of the data via the one ormore uplink radio resources). The reference time may further comprise atime offset (e.g., predefined or RRC-configured). For example, thereference time may be the subframe (or slot) that comprise the end ofthe corresponding PUSCH transmission, plus time offset. For example, thereference time may be the first PDCCH occasion from the end of thecorresponding PUSCH transmission, plus time offset.

The wireless device may receive a control message (e.g., DCI) via PDCCHduring the time window (e.g., ResponseWindowTimer is running). Forexample, the received control message (e.g., DCI) may be with CRCscrambled by the RNTI that the wireless device receives for transmissionvia the one or more radio resource(s) in a Non-RRC_CONNECTED state. Thecontrol message (e.g., DCI) may comprise an uplink grant forretransmission of the data. The wireless device may (re-)start the timewindow (e.g., ResponseWindowTimer) after or in response to receiving theuplink grant. For example, the time window (re-)start at the last slot(subframe, symbol) of a PUSCH transmission corresponding to theretransmission indicated by the uplink grant. For example, the timewindow (re-)start at the first PDCCH occasion from the end of the PUSCHtransmission corresponding to the retransmission indicated by the uplinkgrant. The control message (e.g., DCI) may indicate acknowledgement(e.g., L1 ACK) for the transmission of the data via the one or moreradio resource(s) in the Non-RRC_CONNECTED state. In this case, thewireless device may determine to stop the time window (e.g.,ResponseWindowTimer), and/or determine that the transmission of the datavia the one or more radio resources(s) is successful. The controlmessage (e.g., DCI) may comprise a downlink assignment of PDSCHcomprising the MAC PDU. If the wireless device decodes the MAC PDUsuccessfully, the wireless device may determine to stop the time window(e.g., ResponseWindowTimer), and/or determine that the transmission ofthe data via the one or more radio resources(s) is successful. Thecontrol message (e.g., DCI) may indicate a failure of the transmissionof the data (e.g., fallback). The wireless device may determine to stopthe time window (e.g., ResponseWindowTimer), e.g., after or in responseto receiving the control message indicating the failure (e.g.,fallback). The wireless device may determine the transmission of thedata via the one or more radio resource(s) has failed, e.g., after or inresponse to receiving the control message indicating the failure (e.g.,fallback). The wireless device may initiate a random access procedure,e.g., after or in response to receiving the control message indicatingthe failure (e.g., fallback). The wireless device may initiate a randomaccess procedure, e.g., after or in response to receiving the controlmessage indicating the failure (e.g., fallback). The wireless device maydetermine that the time window (e.g., ResponseWindowTimer) expires. thewireless device may determine that the preconfigured uplink grant asskipped, the PUR transmission has failed, after or in response to theexpiry of the time window.

A wireless device and/or a base station may use HARQ operation(s) and/orprocess(es) for one or more retransmissions of uplink transmission in aNon-RRC_CONNECTED state. For example, a wireless device may transmitdata packet(s) via one or more uplink radio resources configured for theNon-RRC_CONNECTED state (e.g., as shown in FIG. 17 ). The wirelessdevice may monitor a PDCCH after or in response to transmitting the datapacket(s), e.g., while keeping an RRC state as a Non-RRC_CONNECTEDstate. The wireless device may receive, via the PDCCH, DCI that mayindicate an uplink grant for a retransmission of the data packet(s). Theuplink grant may indicate, as an uplink radio resource for theretransmission, one of the one or more uplink radio resources. Theuplink grant may indicate, for the retransmission, the uplink radioresource that is independent of (e.g., allocated separately from) theone or more uplink radio resources. The wireless device may receive,e.g., instead of the uplink grant, an indication (e.g., different typeof DCI) that indicates to perform an RA procedure. The indication mayindicate a failure of the transmission of the data packet(s). Thewireless device may transition to the RRC CONNECTED state, e.g., an RRCconnection setup procedure and/or an RRC resume procedure. The wirelessdevice may initiate (or perform) the RRC connection setup procedureand/or the RRC resume procedure based on an RA procedure. The wirelessdevice may initiate the RA procedure based on receiving the indication(e.g., that indicates that the wireless device performs the RAprocedure). The wireless device may initiate the RA procedure based onreceiving a paging message (e.g., that indicates that the wirelessdevice performs the RA procedure) and/or based on an uplink packetarrival. The one or more uplink radio resources configured for theNon-RRC_CONNECTED state may not be used while the wireless device is inthe RRC CONNECTED state. The wireless device may not transmit (and/ormay stop to transmit) a data packet via the one or more uplink radioresources, e.g., if the RRC state is the RRC_CONNECTED state. Forexample, the wireless device may release (clear, deactivate, suspend,and/or discard) the one or more uplink radio resources configured forthe Non-RRC_CONNECTED state and/or uplink grant(s) indicating the one ormore uplink radio resources after or in response to the RRC state istransitioned to the RRC CONNECTED state. For example, the wirelessdevice may suspend the one or more uplink radio resources configured forthe Non-RRC_CONNECTED state and/or uplink grant(s) indicating the one ormore uplink radio resources after or in response to the RRC state istransitioned to the RRC CONNECTED state.

The wireless device may transmit message(s) (e.g., RRC message(s) suchas PURConfigurationRequest) that requests one or more parameters of(pre-)configured grant(s) indicating one or more uplink radio resourcesin a Non-RRC_CONNECTED state (e.g., RRC_INACTIVE and/or RRC_IDLE). Thewireless device may initiate a procedure, e.g., UE-initiated procedure,to transmit the message(s). The wireless device may transmit themessage(s) in response to receiving a request from a base station, e.g.,BS-initiated procedure. The wireless device may transmit the message(s)while the wireless device is in any of RRC states, RRC_CONNECTED,RRC_INACTIVE, and/or RRC_IDLE. The wireless device may transmit themessage(s) while the wireless device is in particular RRC state(s). Forexample, the wireless device may transmit the message(s) while thewireless device is in the Non-RRC_CONNECTED state. For example, thewireless device may transmit the message(s) while the wireless device isin the RRC_CONNECTED state. The messages may indicate data trafficinformation. For example, the messages may indicate a number ofoccasions of one or more uplink radio resources in the Non-RRC_CONNECTEDstate, e.g., an example parameter, requestedNumOccasions. For example,the messages may indicate a periodicity of one or more uplink radioresources in the Non-RRC_CONNECTED state, e.g., an example parameterrequestedPeriodicity. For example, the messages may indicate a TB sizeof data packet transmitted via one or more uplink radio resources in theNon-RRC_CONNECTED state, e.g., an example parameter, requestedTBS. Forexample, the messages may indicate a time offset for one or more uplinkradio resources in the Non-RRC_CONNECTED state, e.g., an exampleparameter, requestedTimeOffset. The wireless device may not receive(e.g., expect to receive) a response to the message(s) from the basestation. For example, the wireless device may receive, from the basestation, one or more configuration parameters for transmission of uplinkdata via the one or more uplink radio resources in the Non-RRC_CONNECTEDstate.

A wireless device may be configured with an operating band of a cell fortransmission in a Non-RRC_CONNECTED state. The operating band for thetransmission may be a carrier bandwidth. The operating band may comprisea DL band and/or a UL band. The operating band for the transmission maybe a BWP. The BWP may comprise a DL BWP (e.g., the DL band) and/or a ULBWP (e.g., the UL band). For example, the wireless device may receivemessage(s) (e.g., RRC message(s) and/or RRC release message) comprisinga configuration of the operating band for transmission/reception withthe Non-RRC_CONNECTED state in the cell. The message(s) may indicate theconfiguration based on the number of RB (or PRB) and a frequencylocation (e.g., a position of a center frequency). The configuration mayindicate a numerology (e.g., subcarrier spacing) used in the operatingband. The configuration may indicate separate numerologies (e.g.,subcarrier spacings) for the DL band (e.g., DL BWP) and the UL band(e.g., UL BWP). The numerologies (e.g., subcarrier spacings) configuredfor the DL band (e.g., DL BWP) and the UL band (e.g., UL BWP) may bedifferent or the same.

The message(s) may indicate the location and the range of the operatingband (e.g., start, size and/or center frequency and bandwidth, and thelike). The location and the range of the operating band (e.g., start,size and/or center frequency and bandwidth, and the like) may be definedin terms of a resource unit (e.g., RB and/or PRB), e.g., as the multipleof the resource unit. The location and the range of the operating bandmay be at least a part of one carrier of the cell. The message(s) mayindicate the location and the range of the operating band based on afrequency offset and a bandwidth with respect to a center frequency ofthe carrier bandwidth of the cell. The message(s) may indicate thelocation and the range of the operating band based on the frequencyoffset and the bandwidth of the operating band with respect to thecenter frequency at which a synchronization signal detected by thewireless device is located (e.g., initial BWP).

The message(s) may indicate numerology information (e.g., μ and/orsubcarrier spacing) used in the operating band. The wireless device maydetermine the RE structure from the numerology information. themessage(s) may comprise configuration parameters of control channel(s)(e.g., PDCCH and/or PUCCH), data channel(s) (e.g., PDSCH and/or PUSCH),and/or reference signals (SSB(s), CSI-RS(s), and/or SRS(s)). Themessage(s) may indicate the frequency location(s) of the controlchannel(s), data channel(s), and/or reference signals based on frequencyoffset(s) with respect to a reference location in the operating band.For example, the reference location may be a start (and/or end) point ofa first RB matches a start (and/or end) point of the operating band. Forexample, the one or more radio resource(s) in a Non-RRC_CONNECTED statemay be allocated to the start point (e.g., with a frequency offset fromthe reference location) with a size defined in terms of the number ofRBs (or PRBs). The wireless device may determine the location and/orsize of the control channel(s), the data channel(s), and/or thereference signals based on the determined RE structure.

The one or more radio resource(s) in a Non-RRC_CONNECTED state may beallocated in the operating band comprising one or more sub-bands (e.g.,BWPs). For example, the one or more radio resource(s) in theNon-RRC_CONNECTED state may be allocated to a particular sub-band in theoperating band. For example, the message(s) that the wireless devicereceives may indicate the operating band comprising one or moresub-bands (e.g., BWPs). The message(s) may indicate one or moresub-bands with separate locations (e.g., in terms of frequencylocation), separate sizes (e.g., in terms of bandwidth), and/or separatenumerology (e.g., subcarrier spacing). The RE structure for configuringthe one or more sub-bands and the RE structure for configuring theoperating band may be different. The DL band (e.g., DL BWP) and the ULband (e.g., UL BWP) may be configured separately. For example, the DLband and the UL band may have different configuration information, e.g.,in terms of the frequency location and the numerology (e.g., subcarrierspacing). For example, the wireless device may receive a DL controlmessage (e.g., DCI via PDCCH) and/or DL data (e.g., transport block viaPDSCH) based on the information of the operating band (and/or sub-band)configured in the DL band. The wireless device may transmit a UL control(e.g., PUCCH) and/or UL data (e.g., transport block via PUSCH) based onthe information of the operating band (and/or sub-band) configured inthe UL band. For example, the one or more radio resource(s) in theNon-RRC_CONNECTED state may be allocated per a sub-band. For example,the frequency location and/or a size of the one or more radioresource(s) may be with respect to the sub-band.

For the transmission via the one or more radio resource(s) in aNon-RRC_CONNECTED state, a base station may transmit message(s) (e.g.,RRC message(s)) to a wireless device to configure configurationparameters. The configuration parameters may comprise one or more fieldsindicating at least one of following: the antenna port(s) to be used forthe transmission via one or more radio resource(s) in theNon-RRC_CONNECTED state; DMRS configuration used for the transmissionvia the one or more radio resource(s) in the Non-RRC_CONNECTED state; avalue of the (pre-)configured grant timer (e.g., the (pre-) configuredgrant timer may be in multiples of periodicity); the frequency domainresource allocation; a frequency hopping configuration (e.g., Intra-slotfrequency hopping and/or Inter-slot frequency hopping. If the field isabsent, frequency hopping is not configured); frequency hopping offset,e.g., used when frequency hopping is enabled; the MCS table the wirelessdevice may use for PUSCH (e.g., PUSCH with and/or without transformprecoding) the transmission via the one or more radio resource(s) in theNon-RRC_CONNECTED state, e.g., if the field is absent the wirelessdevice may determine a predefined MCS (e.g., qam64); The modulationorder, code rate and/or TB size of the transmission via the one or moreradio resource(s); The number of HARQ processes configured for thetransmission via the one or more radio resource(s) in theNon-RRC_CONNECTED state; uplink power control parameter(s) for thetransmission via the one or more radio resource(s), e.g., indicatorand/or index of closed loop uplink power control, one or more referencepower values (e.g., p0) and/or pathloss scaling value (e.g., Alpha);Periodicity of the one or more radio resource(s), e.g., a validperiodicity value may be determined (pre-defined) based on thenumerology (e.g., subcarrier spacing), and/or the periodicity may be anabsolute time value and/or defined in terms of TTI (symbol, slot,subframe, system frame, and/or any combination thereof); RBG size forPUSCH the transmission via the one or more radio resource(s); aredundancy version (RV) sequence (e.g., [0 2 3 1], [0 3 0 3]) for thetransmission via the one or more radio resource(s); a number ofrepetitions of the transmission via the one or more radio resource(s);activation type indicator indicating whether an additional activationmessage (e.g., DCI, MAC CE, and/or RRC) is required to activate the oneor more radio resource(s) (e.g., FIG. 18A and FIG. 18B); SRS resourceindicator indicating the SRS resource to be used; time domain allocationindicating a start symbol (e.g., stat symbol number (or symbol offset) Sused to determine that the Nth uplink grant) and length L (e.g., thevalue of the time domain allocation may be a combination of start symboland length); PUSCH mapping type of the transmission via the one or moreradio resource(s); a time domain offset defined with respect to a timereference (e.g., SFN=0 and/or timeReferenceSFN); an indicator indicatingwhether a beta offset value is configured dynamically orsemi-statically, wherein the beta offset value is used to determine anuplink power of and/or UCI multiplexing of the PUSCH transmission viathe one or more radio resource(s).

The one or more radio resource(s) may be configured with a particularBWP. For example, the wireless device may receive message(s) (e.g., RRCmessage(s)) comprising configuration parameters of the particular BWP.The particular BWP may comprise DL BWP and/or UL BWP. The configurationparameters may indicate a numerology (e.g., subcarrier spacing) used inthe particular BWP. The configuration parameters may indicate anumerology applied to the DL BWP and/or the UL BWP. The configurationparameters may comprise separate fields and/or indicators indicatingnumerologies, each used in DL BWP and/or UL BWP. The numerologies usedin DL BWP and/or UL BWP may be the same or different. The configurationparameters may indicate radio resource configuration parameters of DLand/or UL control channel (e.g., PDCCH and/or PUCCH) used fortransmission via the one or more radio resource(s). The configurationparameters may radio resource configuration parameters of DL and/or ULdata channel (e.g., PDSCH and/or PUSCH) used for transmission via theone or more radio resource(s). The DL control and/or data channels(e.g., PDCCH and/or PDSCH) may be configured within the DL BWP. The ULcontrol and/or data channels (e.g., PUCCH and/or PUSCH) may beconfigured within the UL BWP.

The particular BWP may be an initial BWP. For example, the DL BWP of theparticular BWP may be an initial DL BWP. For example, the UL BWP of theparticular BWP may be an initial UL BWP. The particular BWP may beconfigured separately from the initial BWP. For example, the DL BWP ofthe particular BWP may be different form the initial DL BWP. Forexample, the UL BWP of the particular BWP may be different from initialUL BWP. For example, the one or more radio resource(s) may be associatedwith a DL BWP and/or a UL BWP. For example, PDCCH (e.g., ACK, NACK,and/or fallback response(s) to the transmission via the one or moreradio resource(s)) and/or PDSCH (e.g., RRC response to the RRC messagetransmitted via the one or more radio resource(s)) related to thetransmission via the one or more radio resource(s) may be configuredwith the DL BWP. For example, PUCCH (e.g., ACK and/or NACK response tothe PDSCH) and/or PUSCH (e.g., data via the one or more radioresource(s)) related to the transmission via the one or more radioresource(s) may be configured with the UL BWP. The wireless device maydetermine that the particular BWP (e.g., DL BWP and/or UL BWP) is theinitial BWP (e.g., initial DL BWP and/or initial UL BWP, respectively),e.g., if field(s) indicating the configuration (e.g., frequencylocation, bandwidth, and/or numerology (e.g., subcarrier spacing)) ofthe particular BWP, e.g., that is different from the initial BWP, areabsent in the configuration parameters indicating the one or more radioresource(s).

The particular BWP may be a last BWP that the wireless device used inRRC_CONNECTED. For example, the DL BWP of the particular BWP may be alast DL BWP that the wireless device used in an RRC_CONNECTED state. Forexample, the UL BWP of the particular BWP may be a last UL BWP that thewireless device used in RRC_CONNECTED. For example, the wireless devicemay transition to a Non-RRC_CONNECTED (e.g., RRC_INACTIVE and/orRRC_IDLE) state from the RRC_CONNECTED state. The BWP (e.g., the last DLBWP and/or the last UL BWP) that the wireless device uses in theRRC_CONNECTED state may be used in the transitioned theNon-RRC_CONNECTED state. The wireless device may determine that theparticular BWP (e.g., DL BWP and/or UL BWP) is the BWP (e.g., the lastDL BWP and/or the last UL BWP, respectively), e.g., if field(s)indicating the configuration (e.g., frequency location, bandwidth,and/or numerology (e.g., subcarrier spacing)) of the particular BWP,e.g., that is different from the last BWP, are absent in theconfiguration parameters indicating the one or more radio resource(s).

The particular BWP may be configured separately from the initial BWP.For example, the DL BWP of the particular BWP may be different form theinitial DL BWP. For example, the UL BWP of the particular BWP may bedifferent from initial UL BWP. For example, the one or more radioresource(s) may be associated with a DL BWP and/or a UL BWP. Forexample, PDCCH (e.g., ACK, NACK, and/or fallback response(s) to thetransmission via the one or more radio resource(s)) and/or PDSCH (e.g.,RRC response to the RRC message transmitted via the one or more radioresource(s)) related to the transmission via the one or more radioresource(s) may be configured with the DL BWP. For example, PUCCH (e.g.,ACK and/or NACK response to the PDSCH) and/or PUSCH (e.g., data via theone or more radio resource(s)) related to the transmission via the oneor more radio resource(s) may be configured with the UL BWP.

FIG. 23 is an example of one or more radio resource(s) in a BWP (e.g.,DL BWP and/or UL BWP) as per an aspect of an embodiment of the presentdisclosure. The wireless device may receive message(s) (e.g., broadcastmessage(s) and/or wireless device specific RRC message) comprisingconfiguration parameters of an initial BWP (e.g., initial DL BWP and/orinitial UL BWP). The initial BWP may be for a cell search and/or aninitial/random access. For example, the wireless device may receiveSSB(s) (e.g., cell-defining SSB) via the initial DL BWP. For example,the wireless device may perform a random access procedure via theinitial BWP. For example, the wireless device may transmit Msg1, Msg3and/or Msg A via the initial UL BWP. The wireless device may receiveMsg2, Msg4 and/or Msg B via the initial DL BWP. The one or more radioresource(s) configured for transmission in Non-RRC_CONNECTED may beconfigured in a BWP different from the initial BWP. The BWP may be alast BWP that the wireless device uses in the RRC_CONNECTED state (e.g.,before transitioning to the Non-RRC_CONNECTED state). The BWP may be fortransmission and/or reception for the wireless device inNon-RRC_CONNECTED. The one or more radio resource(s) for thetransmission may be configured in the UL BWP of the BWP. The PDCCHand/or PDSCH may be configured in the DL BWP of the BWP. The wirelessdevice may deactivate the BWP, e.g., if an RRC state of the wirelessdevice changes (e.g., to the RRC_CONNECTED state). The one or more radioresource(s) and/or PUCCH associated with the transmission in theNon-RRC_CONNECTED state may be configured in an initial UL BWP. ThePDCCH and/or PDSCH associated with the transmission in theNon-RRC_CONNECTED state may be configured in an initial DL BWP. Themessage(s) may indicate whether the BWP is configured separately fromthe initial BWP.

A wireless device may perform, with a base station, a downlink and/oruplink beam management in the Non-RRC_CONNECTED state. The downlinkand/or uplink beam management may comprise a downlink and/or uplink beammeasurement procedure, (re-) configuration of one or more beams, a beamactivation of the one or more beams, a beam selection among the one ormore beams. The downlink and/or uplink beam management may comprise abeam failure detection and/or beam failure recovery procedures.

An indicator of a reference signal in the downlink and/or uplink beammanagement may indicate a beam (e.g., TX beam and/or RX beam of thewireless device) to use in a Non-RRC_CONNECTED state. For example, awireless device may receive message(s) (e.g., RRC message(s)) comprisingconfiguration parameters of one or more radio resource(s) in theNon-RRC_CONNECTED state. The configuration parameters may indicate oneor more reference signals. The one or more reference signals maycomprise an SSB identified by an SSB index/identifier, a CSI-RSidentified by a CSI-RS index/identifier (and/or CSI-RS resourceindex/identifier). The one or more reference signals may comprise an SRSidentified by an SRS index/identifier (e.g., SRS resourceindex/identifier, SRS resource set index/identifier, and/or acombination thereof). The reference signal may represent and/or indicatea particular beam. For example, the SSB may represent and/or indicate awide beam. For example, the CSI-RS may represent and/or indicate anarrow beam. For example, the SRS may represent and/or indicate a TXbeam of the wireless device.

The configuration parameters in the message(s) may comprise indicator(s)indicating which reference signal(s) are associated with whichtransmission (e.g., PUSCH, PUCCH, and/or SRS) and/or reception (e.g.,PDCCH and/or PDSCH). A reference signal may be configured for radio linkmonitor, radio link recovery, and/or transmission and/or reception in anNon-RRC_CONNECTED state.

For example, the configuration parameters may comprise indicator(s)indicating which reference signal(s) are associated with data reception(e.g., PDSCH) and/or control signal (e.g., PDCCH) reception in aNon-RRC_CONNECTED state. For example, the data and/or the control signalmay be associated with the transmission via the one or more radioresource(s) in the Non-RRC_CONNECTED state. For example, the receptionmay be for receiving a response (e.g., RRC response via PDSCH and/or L1ACK/NACK/fallback via PDCCH) to the transmission. For example, theindicator(s) may parameter(s) for configuring a QCL relationship betweenone or more DL reference signals (e.g., SSBs and/or CSI-RSs) and theDM-RS ports of the PDSCH, the DM-RS port of PDCCH, and/or the CSI-RSport(s) of a CSI-RS resource. The parameter(s) may comprise one or moreTCI states. Each of the one or more TCI state may comprise at least oneof following: one or more DL RS(s) (e.g., SSB(s), CSI-RS(s), anycombination thereof), cell index/identifier, BWP index/identifier,and/or QCL relationship type (e.g., the one or more large-scaleproperties). For example, the indicator(s) may be a TCI state of aparticular channel configuration (e.g., PDSCH, PDCCH (e.g., CORESET)).For example, the PDSCH and/or PDCCH (e.g., CORESET) configuration maycomprise at least one of the one or more TCI states. For example, a TCIstate of PDSCH may indicate a QCL relationship between one or more DLreference signals (e.g., SSBs and/or CSI-RSs) and the DM-RS ports of thePDSCH. The wireless device may determine RX beam(s) used to receive datavia the PDSCH based on the TCI state (e.g., QCL relationship of the TCIstate). For example, a TCI state of PDCCH may indicate a QCLrelationship between one or more DL reference signals (e.g., SSBs and/orCSI-RSs) and the DM-RS ports of the PDCCH. The wireless device maydetermine RX beam(s) used to receive control signal(s) via the PDCCHbased on the TCI state (e.g., QCL relationship of the TCI state).

A wireless device may receive one or more message(s) that(re-)configures, updates, and/or activates the TCI state(s) of PDSCHand/or PDCCH (e.g., CORESET). For example, a first control message(e.g., an RRC message) that the wireless device receives may indicate atleast one TCI state to be used for the PDSCH and/or PDCCH (e.g.,CORESET). For example, a first control message (e.g., an RRC message)that the wireless device receives may indicate one or more TCI states. Asecond control message (e.g., another RRC message, a DCI and/or MAC CE)that the wireless device receives may indicate at least one of the oneor more TCI states to be used for the PDSCH and/or PDCCH (e.g.,CORESET). For example, a first control message (e.g., an RRC message)that the wireless device receives may indicate one or more TCI states. Asecond control message (e.g., an RRC message, MAC CE, and/or DCI) thatthe wireless device receives may indicate (or activate) at least firstone of the one or more TCI states. A third control message (e.g., an RRCmessage, MAC CE, and/or DCI) that the wireless device receives mayindicate at least second one of the at least first one of the one ormore TCI states to be used for the PDSCH and/or PDCCH (e.g., CORESET).

The wireless device may receive the configuration parameters comprisingindicator(s) indicating which reference signal(s) are associated withthe data (e.g., PUSCH) and/or control signal (e.g., PUCCH) transmissionassociated with the transmission via the one or more radio resource(s).

For example, the indicator(s) may comprise a spatial relationinformation. The spatial relation information may be for transmission(s)via PUSCH, PUCCH, and/or SRS. The wireless device may determine (e.g.,identify) a particular spatial relation information based an indexand/or identifier of the particular spatial relation information. Thespatial relation information may indicate at least one of following:cell index/identifier, one or more DL RS s (e.g., SSB(s), CSI-RS(s),and/or any combination thereof), SRS resource index/identifier, BWPindex/identifier, pathloss reference RS index/identifier, and/or powercontrol parameter(s). The wireless device may determine antenna portsand/or precoder used for transmission(s) via PUSCH and/or PUCCH based onthe spatial relation information.

For example, the indicator(s) may be the spatial relation information ofa particular channel configuration (e.g.,srs-spatial-relation-information for PUSCH and/orpucch-spatial-relation-information of PUCCH). For example, the PUSCHconfiguration may comprise at least one spatial relation information.For example, the PUCCH configuration may comprise at least one spatialrelation information. The spatial relation information of the PUSCH maybe different from the one of the PUCCH. The spatial relation informationof the PUSCH may be the same as the one of the PUCCH. The spatialrelation information(s) of the PUSCH and PUCCH may be configuredseparately and/or independently. There may be one or more spatialrelation information(s) applied to (and/or used for) the PUSCH and thePUCCH.

The wireless device may determine antenna ports and/or precoder used forthe PUSCH based on the spatial relation information of the PUSCH. Forexample, the wireless device receives message(s) comprisingconfiguration parameters of transmission via one or more radioresource(s) in a Non-RRC_CONNECTED state. The configuration parameters(e.g., SRS resource indicator) may indicate an SRS resource of an SRSresource set. The SRS resource may comprise spatial relationinformation. The wireless device may determine, for the transmission viathe one or more radio resource(s), to use the same antenna port(s) asthe SRS port(s) of the SRS resource. The wireless device may transmit,based on the determination, data via the one or more radio resource(s)using the same antenna port(s).

For example, the wireless device may determine antenna ports and/orprecoder used for the PUCCH based on the spatial relation information ofthe PUCCH. For example, the wireless device receives message(s)comprising configuration parameters of PUCCH in a Non-RRC_CONNECTEDstate. The wireless device may transmit uplink control signal(s) via thePUCCH for HARQ feedback (e.g., ACK or NACK) to PDSCH in theNon-RRC_CONNECTED state, for SR transmission(s), and/or measurementreport(s). The configuration parameters (e.g., PUCCH spatial relationinformation) may indicate the spatial setting (e.g., precoder and/orspatial domain filter) for PUCCH transmission and the parameters forPUCCH power control. The wireless device may determine, for the PUCCHtransmission in the Non-RRC_CONNECTED state, a spatial domain filterused for a reception of a DL RS indicated by the spatial relationinformation. For example, if the spatial relation information for thePUCCH comprises an SSB index/identifier of an SSB, the wireless devicemay transmit the PUCCH using a same spatial domain filter as for areception of the SSB for a cell. For example, if the spatial relationinformation for the PUCCH comprises a CSI-RS index/identifier (e.g.,NZP-CSI-RS resource index/identifier) of a CSI-RS, the wireless devicemay transmit the PUCCH using a same spatial domain filter as for areception of the CSI-RS for a cell. For example, if the spatial relationinformation for the PUCCH comprises an SRS index/identifier of an SRS(e.g., SRS resource), the wireless device may transmit the PUCCH using asame spatial domain filter as for a transmission of the SRS for a celland/or UL BWP.

A wireless device may receive one or more message(s) that(re-)configures, updates, and/or activates the spatial relationinformation of PUSCH, PUCCH, and/or SRS. For example, a first controlmessage (e.g., an RRC message) that the wireless device receives mayindicate at least one spatial relation information to be used for thePUSCH, PUCCH, and/or SRS. For example, a first control message (e.g., anRRC message) that the wireless device receives may indicate one or morespatial relation information(s). A second control message (e.g., anotherRRC message, a DCI and/or MAC CE) that the wireless device receives mayindicate at least one of the one or more spatial relation information(s)to be used for the PUSCH, PUCCH, and/or SRS. For example, a firstcontrol message (e.g., an RRC message) that the wireless device receivesmay indicate one or more spatial relation information(s). A secondcontrol message (e.g., an RRC message, MAC CE, and/or DCI) that thewireless device receives may indicate (or activate) at least first oneof the one or more spatial relation information(s). A third controlmessage (e.g., an RRC message, MAC CE, and/or DCI) that the wirelessdevice receives may indicate at least second one of the at least firstone of the one or more spatial relation information(s) to be used forthe PUSCH, PUCCH, and/or SRS.

FIG. 24 is an example of beam management for transmission and/orreception in an Non-RRC_CONNECTED state as per an aspect of anembodiment of the present disclosure. The wireless device may receivemessage(s) comprising configuration parameters of transmission/receptionin the Non-RRC_CONNECTED state. The configuration parameters mayindicate configurations of radio resources of PUSCH, PDCCH, PDSCH,and/or PUCCH used in the Non-RRC_CONNECTED state. The configurationparameters may indicate one or more radio resource(s) for uplinktransmission (e.g., via PUSCH) in the Non-RRC_CONNECTED state. Theconfiguration parameters may indicate which beam(s) (e.g., referencesignal(s)) are used to transmit (e.g., via PUSCH and/or PUCCH) orreceive (e.g., via PDSCH and/or PDCCH) in the Non-RRC_CONNECTED state.For example, in FIG. 24 , the wireless device transmits, using the 1stbeam, data via one or more radio resource(s) in the Non-RRC_CONNECTEDstate. The wireless device may start to monitor PDCCH using the 3rdbeam. The wireless device may receive, via the PDCCH, DCI that comprisedownlink assignment of PDSCH. The wireless device may receive the PDSCHusing the 4th beam. The wireless device may transmit, via PUCCH, an HARQfeedback (e.g., ACK or NACK) using the 2nd beam. The base station mayreceive or transmit data using different beams and/or a same beam, e.g.,the 1st beam for PUSCH reception, the 2nd beam for PDCCH transmission,the 3rd beam for PDSCH transmission, and/or the 4th beam for PUCCHreception. The wireless device may receive second message(s) (e.g., RRCmessage, MAC CE, DCI, and/or a combination thereof) reconfigure, change,activate/deactivate, and/or update the beam configuration of the PUSCH,PDCCH, PDSCH, and/or PUCCH.

In multi-beam operations, a cell may transmit a plurality of DL RSs(e.g., a plurality of SSBs, CSI/RS, and/or the like), e.g., using aplurality of beams (e.g., TX beams of the cell). One or more radioresources in a Non-RRC_CONNECTED state that are configured in the cellmay be configured with a plurality of beams. For example, channel(s)(e.g., the PDCCH, PDSCH, PUSCH and/or PUCCH) for transmission and/orreception in the Non-RRC_CONNECTED state may be associated with a firstbeam of the plurality of the beams. For example, a wireless device mayreceive message(s) (e.g., RRC message, MAC CE, DCI, and/or anycombination thereof) comprising radio resource configuration parametersindicating the association between the channel(s) and the first beam.For example, the radio resource configuration parameters may indicatethat a beam configuration (e.g., TCI and/or spatial relationinformation) of the channel(s) comprises a first DL RS of the pluralityof DL RSs. The first DL RS may represent and/or indicate the first beam(e.g., as shown in FIG. 24 ). For example, one of the plurality of DL RSmay be associated with one or more channels (e.g., the PDCCH, PDSCH,PUSCH, and/or PUCCH). The wireless device may determine, based on theassociation, antenna port(s) and/or precoder (e.g., spatial domainfilter) to be used for the transmission and/or the reception performedvia the channel(s). For example, the wireless device may determine theantenna port(s) and/or the precoder (e.g., spatial domain filter) basedon one(s) that used for receiving the first DL RS.

A wireless device may perform, with a base station, beam failuredetection and/or beam failure recovery procedures in theNon-RRC_CONNECTED state. In the present disclosure, beam failuredetection and/or beam failure recovery procedures may be referred to asradio link monitoring and/or link recovery procedures. For example, thewireless device determines the beam failure detection via the radio linkmonitoring procedure. The wireless device may perform the beam failurerecovery procedure to determine a better beam as the link recoveryprocedure. A cell that the wireless device performs the beam failuredetection and/or beam failure recovery procedures may be the one wherethe wireless device is configured with one or more uplink radioresources in the Non-RRC_CONNECTED state

In an example, a wireless device may receive message(s) (e.g., RRCmessage(s)) comprising configuration parameters of one or more radioresource(s) of a cell in the Non-RRC_CONNECTED state. The configurationparameters may indicate one or more reference signals of the cell. Theone or more reference signals may comprise an SSB identified by an SSBindex/identifier, a CSI-RS identified by a CSI-RS index/identifier(and/or CSI-RS resource index/identifier). The one or more referencesignals may comprise an SRS identified by an SRS index/identifier (e.g.,SRS resource index/identifier, SRS resource set index/identifier, and/ora combination thereof). The reference signal may indicate a particularbeam used for the beam failure detection and/or beam failure recoveryprocedures of the cell. For example, the SSB may represent and/orindicate a wide beam of the cell. For example, the CSI-RS may representand/or indicate a narrow beam of the cell. For example, the SRS mayrepresent and/or indicate a TX beam of the wireless device. A wirelessdevice may determine a reference signal associated with a particularchannel as the one used for the beam failure detection and/or beamfailure recovery procedures. The particular channel may be a PDCCH ofthe cell. The particular channel may be one or more uplink radioresources (e.g., PUSCH) used for uplink transmission in aNon-RRC-CONNECTED state.

The configuration parameters in the message(s) may comprise indicator(s)indicating which reference signal(s) are associated with radio linkmonitoring (e.g., beam failure detection procedure) of the cell and/orlink recovery (e.g., beam failure recovery procedure) of the cell. Forexample, the radio link monitoring and/or link recovery may be fortransmission and/or reception performed in the Non-RRC_CONNECTED state.A reference signal configured for the radio link monitoring may bereferred to as a radio link monitoring RS and/or beam failure detectionresource (or DL RS). For example, the wireless device may determine abeam failure detection of the cell based on monitoring (and/ormeasuring) a beam measurement quantity (e.g., RSRP, RSRQ, RSSI, BLER,and/or the like) of the reference signal configured for the radio linkmonitoring. The reference signal may be configured for the radio linkrecovery. The reference signal configured for the radio link recoverymay be referred to as a candidate beam RS and/or resource. For example,the wireless device may select one of reference signals configured forthe radio link recovery as a candidate beam to recover. The wirelessdevice may determine the one of the reference signals based on beammeasurement quantities (e.g., RSRP, RSRQ, RSSI, BLER, and/or the like)of the reference signals configured for the radio link recovery.

A wireless device may perform a beam failure detection procedure, e.g.,after or in response to receiving RRC message(s) (e.g., RRC releasemessage) comprising configuration parameters of the beam failuredetection procedure of a cell. The wireless device may determine, basedon the beam failure detection procedure, whether current beam(s) (e.g.,DL RS(s)) used for at least one of transmission(s) and/or reception(s)of the cell are in a normal condition or not. It may be referred to as abeam failure if the current beam(s) are not in a normal condition. In anexample, a wireless device may detect and/or determine the beam failureon at least one configured beam (e.g., DL RS) of the cell. For example,the at least one configured beam (e.g., DL RS) may be used fortransmission (e.g., PUSCH and/or PUCCH) via one or more uplink radioresources of the cell in the Non-RRC_CONNECTED state. For example, theat least one configured beam (e.g., DL RS) may be used for reception viaPDCCH and/or PDSCH the cell in the Non-RRC_CONNECTED state. For example,it may be referred to as at least one configured beam (e.g., DL RS)being failed. It may be referred to as a beam failure detection on theat least one configured beam if the wireless device may detect and/ordetermine a beam failure on at least one configured beam. A wirelessdevice may determine the beam failure on the at least one configuredbeam based on a beam failure instance. For example, the wireless devicemay trigger and/or determine the beam failure instance based on a beammeasurement quantity of the at least one configured beam. For example,the beam measurement quantity may be RSRP, RSRQ, and/or BLER of the atleast one configured beam (e.g., the DL RS). For example, the wirelessdevice may trigger, detect, and/or determine the beam failure instanceon at least one configured beam (e.g., DL RS), e.g., if a beammeasurement quantity value (e.g., an RSRP value and/or RSRQ value) ofthe at least one configured beam is lower than a threshold value. Forexample, the wireless device may trigger, detect, and/or determine thebeam failure instance on at least one configured beam (e.g., DL RS),e.g., if a beam measurement quantity value (e.g., a BLER value) of theat least one configured beam is lower than a threshold value.

The at least one beam (e.g. DL RS) may be a configured beam for the beamfailure detection of the cell. The at least one beam may be indicated byan identifier of a DL RS of the cell. For example, the DL RS may be aradio link monitoring RS configured by an RRC message that the wirelessdevice receives from a base station (e.g., via the cell). For example,the DL RS may be an SSB and/or CSI-RS of the cell. For example, awireless device may receive message(s) configuring the at least one beamfor the beam failure detection and/or recovery procedures. Themessage(s) may indicate configuration parameters of the DL RS. Forexample, the configuration parameters may indicate a periodicity of theDL RS, a time offset, time domain allocation within a physical resourceblock (e.g., first OFDM symbol in time domain), frequency domainallocation (e.g., frequency domain allocation within a physical resourceblock, frequency band, and/or the like) of the DL RS, a reference powerand/or a power offset of transmission of the DL RS. The DL RS may be DLBWP specific of the cell. The DL RS may be cell-specific. The wirelessdevice may monitor the DL RS and/or determine the beam failure instancebased on the configuration parameters.

A wireless device may trigger, detect, and/or determine a beam failureof a cell based on counting beam failure instance(s). For example, lowerlayer(s) (e.g., a physical layer) of the wireless device may send anindication of a beam failure instance to a higher layer (e.g., the MACentity) of the wireless device. The indication may be referred to as abeam failure instance indication. The wireless device may determine toperform a beam failure recovery procedure, e.g., if a number of beamfailure instance indications that the wireless device counts is largerthan or equal to a counter threshold value (e.g., a beam failureinstance max-count). For example, the wireless device may determine toperform and/or trigger the beam failure recovery procedure for the cell,e.g., if the wireless device determines at least one beam failureinstance (e.g., higher layer such as MAC entity receives at least onebeam failure instance indication from lower layer(s)).

In example embodiment(s), the wireless device may count the number ofbeam failure instance indications based on a timer (e.g., beam FailureDetection Timer). The wireless device may (re-)start the timer, e.g., ifthe number of beam failure instance indications increases by one. Thewireless device may run the timer during a time interval. For example,the time interval may be a value of the timer (e.g., the beam failuredetection timer). The wireless device may determine that the timerexpires, e.g., if the timer runs for the time interval. The running timeof the timer during the time interval may be continuous. The runningtime of the timer during the time interval may be non-continuous. Forexample, the wireless device may stop (and/or pause) the timer and runthe timer one or more times. The value of the timer and/or the timeinterval may be predefined and/or semi-statically configured by an RRCmessage. For example, if an MAC entity of the wireless device receives abeam failure instance indication from lower layer(s) of the wirelessdevice, the wireless device may increment a value of a counter (e.g.,the BFI counter) by one and/or (re-)start the timer. The wireless devicemay determine whether the value of the counter is larger than or equalto a threshold value, e.g., when the wireless device increment the valueof the counter. The wireless device may determine to perform a beamfailure recovery procedure, e.g., if the value of the counter is largerthan or equal to the threshold value. The wireless device may (re-)setthe value of the counter to an initial value (e.g., zero), e.g., if thetimer expires. The wireless device may (re-)set the value of the counterto an initial value (e.g., zero), e.g., if the beam failure recoveryprocedure successfully completes. The wireless device may (re-)set thevalue of the counter to an initial value (e.g., zero), e.g., if thewireless device receives a message (re-)configuring at least one ofconfiguration parameters of the beam failure detection and recoveryprocedures.

In example embodiment(s), the wireless device may receive, from a basestation, a message configuring a beam failure indication (BFI) counterfor a beam failure detection and/or recovery procedures for a cell inthe Non-RRC_CONNECTED state. The wireless device may set a value of theBFI counter to an initial value (e.g., zero) for the beam failuredetection and/or recovery procedures. For example, the wireless devicemay set a value of the BFI counter to an initial value (e.g., zero),e.g., when the wireless device receives the message comprisingconfiguration parameters, e.g., a counter threshold value of the BFIcounter (e.g., a beam failure instance max-count) and/or a value of thetimer. The wireless device may (re-)start a beam failure detectiontimer, e.g., if a beam failure instance indication is triggered (e.g.,has been received from lower layers). The wireless device may incrementthe BFI counter by one (e.g., example of the BFI counter inspecification is up-counter). The value of the BFI counter may be largerthan or equal to a threshold value (e.g., a beam failure instancemax-count). The wireless device may trigger and/or perform a beamfailure recovery procedure, e.g., if the value of the BFI counter may belarger than or equal to the threshold value. The wireless device may(re-)set the value of the BFI counter to an initial value (e.g., zero).For example, the wireless device may (re-)set the value of the BFIcounter to an initial value (e.g., zero) if the beam failure detectiontimer expires. For example, the wireless device may (re-)set the valueof the BFI counter to an initial value (e.g., zero) if beam failuredetection timer, beam failure instance max-count, and/or any of thereference signals used for beam failure detection are reconfigured byupper layers. For example, the wireless device may (re-)set the value ofthe BFI counter to an initial value (e.g., zero) and/or may stop thebeam failure recovery timer (e.g., if configured) if the wireless devicereceives a response of a beam failure recovery information (e.g.,indication of a beam failure and/or identifier(s) of candidate beam(s))transmitted based on a beam failure recovery procedure.

A wireless device may perform a beam failure recovery procedure for acell, e.g., after or in response to a determination of a beam failuredetection on the cell. The wireless device may switch, based on a beamfailure recovery procedure, at least one beam (e.g., at least one DL RSof the cell) configured for transmission and/or reception to anotherbeam(s) (e.g., another DL RSs of the cell). After or in response to thebeam failure recovery procedure, the wireless device may perform thetransmission and/or reception configured with the another beam(s) (e.g.,the another DL RSs). The beam failure recovery procedure may comprise atleast one of followings: transmitting (e.g., to a base station) one ormore beam failure recovery request messages indicating a beam failure onthe cell, identifier(s) of failed beam(s) (e.g., DL RS(s)) of the cell,and/or one or more candidate beams (e.g., candidate DL RSs) of the cell.The wireless device may receive one or more messages as response(s) tothe one or more beam failure recovery request messages. For example, theone or more messages may indicate a reception of the one or more beamfailure recovery request messages (e.g., an identifier of a contentionresolution ID and/or an identifier of a preamble that the wirelessdevice transmits), an uplink grant, and/or configuration parameters(e.g., reconfigured based on the one or more beam failure recoveryrequest messages) of one or more beams for transmission and/orreception. The wireless device may determine that the beam failurerecovery procedure successfully completes, e.g., after or in response toreceiving the one or more messages.

In multi-beam operations, the wireless device may determine a cellmeasurement quantity value of a cell amongst a plurality of beams of acell. The cell measurement quantity value (e.g., RSRP, RSRQ, RSSI, andthe like) of the cell may be referred to as a serving cell measurement,a measurement quantity of the cell, and/or the like. The wireless devicemay receive one or more DL RSs from the cell (and/or a base station).The cell may use the plurality of beams to transmit the one or more DLRSs. The one or more DL RSs may be SSB(s), CSI-RS, and/or cell-specificRS, and/or any type of RS(s) transmitted from the cell and/or for thewireless device. For example, each of the one or more DL RSs mayrepresent and/or associated with at least one of the plurality of beams.For example, the wireless device may determine the cell measurementquantity value based on measured power value(s) (e.g., RSRP, RSRQ, RSSI,and/or the like) of the one or more DL RSs received from the cell.

In multi-beam operations, a wireless device may determine a cellmeasurement quantity value by a function (e.g., as a linear average) ofthe measured power values (e.g., RSRPs, RSRQ, RSSI, and/or the like) ofthe one or more DL RSs. A measured power value of a DL RS may bereferred to as a beam measurement quantity of the DL RS. For example,the wireless device may determine a cell measurement quantity value asan average (e.g., as a linear average) of the measured power values ofthe one or more DL RSs, and/or beam measurement quantities of the one ormore DL RS.

The wireless device may receive a message (e.g., SIB(s) and/or RRCrelease message) comprising one or more parameters indicating how manyDL RSs (e.g., beams) are used to determine the cell measurement quantityvalue. The one or more parameters may comprise a first parameterindicating that a number of the one or more DL RS s used to determinethe cell measurement quantity value is less than or equal to a firstthreshold value (e.g., nrofSS-BlocksToAverage, and/ormaxRS-IndexCellQual). The one or more parameters may comprise a secondparameter indicating a second threshold value (e.g.,absThreshSS-BlocksConsolidation, and/or threshRS-Index). The wirelessdevice may select, to determine the cell measurement quantity value, atleast one DL RS among the one or more DL RSs. For example, a measuredpower value of the at least one DL RS that the wireless device selectsmay be higher than the second threshold value. For example, the numberof the at least one DL RS may be less than or equal to the firstthreshold value.

Among the one or more DL RSs, there may be M DL RSs whose measured powervalue(s) are higher than the second threshold. For example, if M islarger than the first threshold value, the wireless device may select NDL RSs among the M DL RSs (e.g., N≤the first threshold value). Forexample, the N DL RSs may have the N highest measured power value(s)among the one or more DL RSs. For example, the wireless device mayrandomly select the N DL RSs among the M DL RSs and/or among the one ormore DL RSs.

There may be a case that the first threshold value is not configured. Inthis case, the number of the at least one DL RS that the wireless deviceselects among the one or more DL RSs may be predefined and/orsemi-statically configured (e.g., by an RRC message and/or MIB/SIB). Forexample, if a field indicating the first threshold value is absent(e.g., is not configured and/or indicated) in a message that thewireless device receives, the wireless device may select the cellmeasurement quantity value based on a DL RS as the highest measuredpower value.

There may be a case that the second threshold value is not configured.In this case, the number of the at least one DL RS that the wirelessdevice selects among the one or more DL RSs may be predefined and/orsemi-statically configured (e.g., by an RRC message and/or MIB/SIB). Forexample, if a filed indicating the second threshold value is absent(e.g., is not configured and/or indicated) in a message that thewireless device receives, the wireless device may select the cellmeasurement quantity value based on a DL RS(s) as the highest measuredpower value.

There may be a case that the measured power values the one or more DLRSs are smaller than or equal to the second threshold. In this case, thenumber of the at least one DL RS that the wireless device selects amongthe one or more DL RSs may be predefined and/or semi-staticallyconfigured (e.g., by an RRC message and/or MIB/SIB). For example, thewireless device may select the cell measurement quantity value based ona DL RS(s) as the highest measured power value.

A wireless device may use a cell measurement quantity value of a cell tovalidate transmission (to the cell) and/or reception (from the cell) ina Non-RRC_CONNECTED state. For example, the wireless device maydetermine whether a TA value is valid or not based on the cellmeasurement quantity value (e.g., serving cell RSRP value). For example,the wireless device may determine the TA value for the transmission viaone or more radio resources in a Non-RRC_CONNECTED state, e.g., if atleast one of the following conditions are fulfilled: a TAT is running; acell measurement quantity value (e.g., a measured value of a servingcell RSRP) has not increased by more than an increase threshold value(e.g., since the last TA validation); and/or a cell measurement quantityvalue (e.g., a measured value of a serving cell RSRP) has not decreasedby more than a decrease threshold value (e.g., since the last TAvalidation).

The wireless device may receive one or more DL RS s from the cellconfigured with multi-beam operations. The wireless device may determinea cell measurement quantity value by a function (e.g., as an average, alinear average) of the measured value (e.g., RSRPs, RSRQ, RSSI, and/orthe like) of at least one DL RS of the one or more DL RSs. The wirelessdevice may use measured power value(s) of one or more DL RSs to selectthat at least one DL RS among the one or more DL RS. For example, thewireless device may select N DL RSs (N≥1) among the one or more DL RSsto determine the cell measurement quantity value. For example, measuredvalue(s) of the N DL RSs may be higher than the second threshold value.For example, the measured values of the N DL RSs may be the highest Nvalues among the measured values of the one or more DL RSs. For example,as the wireless device moves

In existing technologies, a wireless device may perform a beam failuredetection and/or recovery procedure for a serving cell in anRRC_CONNECTED state. The wireless device may change the serving cellfrom a first cell to a second cell. For example, the change of theserving cell may be under a network control in the RRC_CONNECTED state.For example, the wireless device may receive a handover message/commandfrom a base station. The handover message/command may indicate thesecond cell as a new serving cell and/or one or more configurationparameters of the second cell. The wireless device may perform a randomaccess procedure to the second cell and may determine the second cell asthe new serving cell after or in response to a determination that therandom access procedure successfully completes. The wireless device maystart to perform the beam failure detection and/or recovery proceduresfor the second cell. Configuration parameters of the beam failuredetection and/or recover procedures may be cell-specific. The wirelessdevice may store the configuration parameters of the beam failuredetection and/or recover procedures for the serving cell. For example,the wireless device may release configuration parameters of the beamfailure detection and/or recover procedures for the first cell, e.g., ifthe wireless device changes the serving from the first cell to thesecond cell.

In a Non-RRC_CONNECTED state, a wireless device may perform a cell(re-)selection procedure one or more times, e.g., with a time intervaland/or a periodicity. For example, the cell reselection procedure may befor the wireless device to select a cell (e.g., a suitable cell) whereto camp on in order to access available services in theNon-RRC_CONNECTED state. One or more services may be available for thewireless device in the cell where the wireless device camps on. Forexample, the one or more services comprise originating emergency callsand/or receiving a public warning message/notification such as ETWS(Earthquake and Tsunami Warning System) notification and/or CMAS(Commercial Mobile Alert System) notification. For example, the suitablecell may be a part of a particular (e.g., selected and/or registered)PLMN and/or a PLMN of the equivalent PLMN list. A measurement (e.g.,cell measurement) of the cell may fulfill one or more criteriapredefined and/or semi-statically configured. In the Non-RRC_CONNECTEDstate, a cell (re-)selection procedure may not be under a networkcontrol. For example, a network may provide and/or transmit one or moreconfiguration parameters required for the cell (re-)selection procedure.The wireless device may perform measurements for cell (re-)selectionprocedure based on the one or more configuration parameters. Thewireless device may select, based on the cell (re-)selection procedure,a different cell to camp on other than the cell where the wirelessdevice currently camp on. A comparison to check which cell is better maybe based on cell-level RSRP measurements (e.g., cell measurementquantity values). The wireless device may not inform the network, in theNon-RRC_CONNECTED state, of a selection of the different cell. Thenetwork may not be able to determine in which cell the wireless deviceis located (camps on), e.g., until the wireless device transmit one ormore messages and/or signals (e.g., area update notification, preamble,Msg3, MsgA, and/or the like) to the network.

A wireless device may receive a message comprising configurationparameters of one or more radio resources used for transmission and/orreception in a Non-RRC_CONNECTED state. For example, the one or moreradio resources may be configured on a cell where the wireless devicemay camp on in the Non-RRC_CONNECTED state. The wireless device mayperform a beam failure detection and/or recovery procedures for thetransmission and/or the reception of the cell, e.g., while the wirelessdevice is camping on the cell. The wireless device may perform a cell(re-)reselection procedure in the cell, e.g., while the wireless deviceis camping on the cell.

The beam failure detection and/or recovery procedures may performed atleast based on one or more beam measurement quantity of DL RS(s). Alower layer (e.g., a physical layer and/or MAC layer) of the wirelessdevice may perform the beam failure detection and/or recovery procedure.

FIG. 25 is an example of a beam failure detection and/or recoveryprocedures as per an aspect of an embodiment of the present disclosure.A wireless device may receive one or more DL RSs from a cell. In FIG. 25, the wireless device receives 4 DL RSs. For example, DL RS4 may be theone configured for the beam failure detection and/or recovery proceduresfor the cell. For example, the wireless device may use DL RS4 fortransmission and/or reception via one or more radio resources configuredto use in a Non-RRC_CONNECTED state. For example, the wireless devicemay be located, at time T1, within an area that the DL RS4 serves. Thewireless device may move toward an area covered by DL RS1 and/or DL RS2in the cell. For example, at time T2, the wireless device may determinea beam failure based on a beam measurement quantity of the DL RS4. Forexample, a value of the beam measurement quantity of the DL RS4 may besmaller than or equal to a threshold value at Time 2. The wirelessdevice may trigger and/or perform a beam failure recovery procedure inresponse to the beam failure. The wireless device may transmit one ormore beam failure recovery requests (e.g., preamble, PUCCH, Msg3, and/orMsgA) indicating DL RS1 and/or DL RS2 as a candidate beam. The wirelessdevice may receive a response to the one or more beam failure recoveryrequests. The wireless device may perform transmission and/or receptionusing the DL RS1 and/or DL RS2 via radio resources configured to use inthe Non-RRC_CONNECTED state.

The cell (re-)selection procedure may be at least based on one or morecell measurement quantities of one or more cells. A higher layer (e.g.,RRC layer) of the wireless device may perform the cell (re-)selectionprocedure.

In an example, the wireless device may receive one or more DL RSs from acell configured with multi-beam operations. The wireless device maydetermine a cell measurement quantity value of the cell by a function(e.g., as an average, a linear average) of the measured value (e.g.,RSRPs, RSRQ, RSSI, and/or the like) of at least one DL RS of the one ormore DL RSs. The wireless device may use measured power value(s) of oneor more DL RSs to select that at least one DL RS among the one or moreDL RS. For example, the wireless device may select N DL RSs (N≥1) amongthe one or more DL RSs to determine the cell measurement quantity value.For example, measured value(s) of the N DL RSs may be higher than thesecond threshold value. For example, the measured values of the N DL RSsmay be the highest N values among the measured values of the one or moreDL RSs. For example, as the wireless device moves

FIG. 26 is an example of a cell (re-)selection procedure as per anaspect of an embodiment of the present disclosure. At time T1, awireless device may camp on Cell 1 in FIG. 26 . The wireless device mayperform the cell (re-)selection procedure one or more times while an RRCstate of the wireless device is a Non-RRC_CONNECTED state. The wirelessdevice may perform measurements for the cell (re-)selection procedure inthe Non-RRC_CONNECTED state. The measurements may comprise cellmeasurement quantities of Cell 1 and Cell 2 in FIG. 26 . At time T1, thewireless device may perform the cell (re-)selection procedure. Forexample, a value of the cell measurement quantity of Cell 1 may behigher than a threshold value and/or highest among the measurements. Thewireless device may move toward Cell 2 away from Cell 1. At Time T2, thewireless device may perform measurements for the cell (re-)selectionprocedure in the Non-RRC_CONNECTED state. The measurements may comprisecell measurement quantities of Cell 1 and Cell 2. At time T2, a value ofthe cell measurement quantity of Cell 2 may be higher than a thresholdvalue and/or highest among the measurements. The wireless device maydetermine to camp on Cell 2 based on the measurements performed at T2.

A problem arises when a wireless device (e.g., higher layer(s) of thewireless device) selects a new cell to camp on based on the cell(re-)selection procedure, while the wireless device (e.g., lowerlayer(s) of the wireless device) triggers and/or performs the beamfailure detection and/or recovery procedure. For example, the wirelessdevice may select the new cell as the wireless device moves away from acell currently being camped on. Moving away from the cell may lead thewireless device (e.g., lower layer(s)) to determine a beam failure onone or more DL RSs of the cell. In this case, based on using existingtechnologies, the wireless device may perform the beam failure detectionand/or recovery procedure in the new cell where the one or more DL RSsare not configured. This results in unnecessary transmission and/orreception of message(s)/signal(s) and unnecessary battery powerconsumption in a Non-RRC_CONNECTED state to resolve the consistency.There is a need to coordinate between beam failure detection/recoveryprocedures and a cell (re-)selection procedure in the Non-RRC_CONNECTEDstate.

FIG. 27 is an example of a cell (re-)selection procedure and/or beamfailure detection/recovery procedures as per an aspect of an embodimentof the present disclosure. At time T1, a wireless device in aNon-RRC_CONNECTED state may camp on Cell 1 in FIG. 26 . For example, thewireless device may receive one or more DL RSs from Cell 1. Cell 1 isthe one that one or more radio resources are configured for the wirelessdevice to perform transmission and/or reception in the Non-RRC_CONNECTEDstate. For example, DL RS4 may be the one configured for the beamfailure detection and/or recovery procedures for Cell 1. For example,the wireless device may use DL RS4 for transmission and/or reception viathe one or more radio resources. The wireless device may perform thecell (re-)selection procedure one or more times while an RRC state ofthe wireless device is a Non-RRC_CONNECTED state. The wireless devicemay perform measurements for the cell (re-)selection procedure in theNon-RRC_CONNECTED state. The measurements may comprise cell measurementquantities of Cell 1 and Cell 2 in FIG. 26 . At time T1, the wirelessdevice may perform the cell (re-) selection procedure. For example, avalue of the cell measurement quantity of Cell 1 may be higher than athreshold value and/or highest among the measurements. The wirelessdevice may determine to camp on Cell 1 based on the value. For example,at Time T1, the wireless device may determine a value of a beammeasurement quantity of the DL RS4 is higher than a threshold, e.g.,which may indicate no beam failure. The wireless device may move towardCell 2 away from Cell 1. For example, at time T2, the wireless devicemay determine a beam failure based on a beam measurement quantity of theDL RS4. For example, a value of the beam measurement quantity of the DLRS4 may be smaller than or equal to a threshold value at Time 2. Thewireless device may trigger and/or perform a beam failure recoveryprocedure for Cell 1 in response to the beam failure. At Time T2, thewireless device may perform measurements for the cell (re-)selectionprocedure in the Non-RRC_CONNECTED state. The measurements may comprisecell measurement quantities of Cell 1 and Cell 2. At time T2, a value ofthe cell measurement quantity of Cell 2 may be higher than a thresholdvalue and/or highest among the measurements. The wireless device maydetermine to camp on Cell 2 based on the measurements performed at T2.

In example embodiment(s) of this specification, a wireless device maydetermine whether to perform the beam failure detection and/or recoveryprocedures in conjunction with the cell (re-)selection procedure. Forexample, the wireless device determine whether to camp on another cellor not, e.g., when the wireless device determines a beam failure and/ordetermines to perform the beam failure detection and/or recoveryprocedure. For example, the wireless device may determine the beamfailure, e.g., if the wireless device camps on a cell for which thewireless device performs the beam failure detection and/or recoveryprocedure. For example, as a triggering and/or determination conditionof the beam failure, the wireless device may determine in which cell thewireless device camps on in an Non-RRC_CONNECTED state. This may preventthe wireless device from performing the beam failure detection and/orrecovery procedure in the new cell where the one or more DL RSs are notconfigured. This may prevent unnecessary transmission and/or receptionof message(s)/signal(s) and unnecessary battery power consumption in aNon-RRC_CONNECTED state.

In example embodiment(s), a wireless device may reset (clear, and/orinitialize) configuration parameters of the beam failuredetection/recovery procedure for a first cell, e.g., after or inresponse to camping on a second cell (e.g., different from the firstcell). For example, the wireless device may stop and/or reset (or clear)one or more timer values that may run during the beam failuredetection/recovery procedure, e.g., after or in response to camping onthe second cell. For example, the wireless device may reset (or clear)one or more counter values that the wireless device increment during thebeam failure detection/recovery procedure, e.g., after or in response tocamping on the second cell. For example, a wireless device may reset,stop, suspend, and/or abort ongoing beam failure detection and/orrecovery procedure, e.g., if a cell where the wireless device performsthe beam failure detection and/or recovery procedure is that the onewhere the wireless device camps on.

FIG. 28 is an example of beam failure detection and/or recoveryprocedure as per an aspect of an embodiment of the present disclosure. Awireless device may receive a message comprising configurationparameters of a cell for a Non-RRC_CONNECTED state. For example, theconfiguration parameters indicate one or more radio resources (e.g.,PURs) used for transmission to and/or reception from the cell in theNon-RRC_CONNECTED state. For example, the configuration parameters mayindicate parameter values of beam failure detection and/or recoveryprocedures for the cell in the Non-RRC_CONNECTED state. The wirelessdevice may receive one or more DL RSs. The wireless device may determinevalues of beam measurement quantities of the one or more DL RS. Thewireless device may determine a beam failure based on the values. Forexample, at least one value of the beam measurement quantity of a DL RS(among the one or more DL RS) may be smaller than or equal to athreshold value one or more times. The DL RS may be configured to beused for the transmission (e.g., PDSCH and/or PUCCH) and/or thereception (e.g., PDSCH and/or PDCCH) during the Non-RRC_CONNECTED state.The wireless device may determine whether a cell to camp on is changed.For example, the wireless device may trigger and/or perform a beamfailure recovery procedure, e.g., if the wireless device camps on thecell. The wireless device may determine a candidate beam as a new beamfor the transmission and/or the reception during the beam failurerecovery procedure. The wireless device may perform one or moretransmission and/or reception using the new beam after or in response tosuccessfully completing the beam failure recovery procedure. Forexample, the wireless device may not trigger, may not perform, may stop(abort), and/or may cancel a beam failure recovery procedure, e.g., ifthe wireless device camps on another cell that is different from thecell.

FIG. 29 is an example of a cell (re-)selection procedure as per anaspect of an embodiment of the present disclosure. A wireless device mayreceive a message comprising configuration parameters of a first cellfor a Non-RRC_CONNECTED state. For example, the configuration parametersindicate one or more radio resources (e.g., PURs) used for transmissionto and/or reception from the first cell in the Non-RRC_CONNECTED state.For example, the configuration parameters may indicate parameter valuesof beam failure detection and/or recovery procedures for the cell in theNon-RRC_CONNECTED state. The wireless device may receive one or more DLRSs of one or more cells while the wireless device camps on the firstcell. The wireless device may determine values of cell measurementquantities of the one or more cells. The wireless device may determineto camp on a second cell based on the values. For example, at least, avalue of cell measurement quantity of the first cell may be smaller thana value of cell measurement quantity of the second cell. The wirelessdevice may trigger and/or perform beam failure detection and/or recoveryprocedures for the first cell. For example, the smaller value of thecell measurement quantity of the first cell may be based on one or morebeam measurement quantities of one or more DL RSs of the first cell.Values (e.g., small values) of the one or more beam measurementquantities may lead the wireless device to trigger and/or perform thebeam failure detection and/or recovery procedures. The wireless devicemay stop and/or abort the (triggered and/or pending) beam failuredetection and/or procedures, after or in response to a determination tocamp on the second cell. The wireless device may reset one or morecounter values and/or timers, e.g., after or in response to adetermination to camp on the second cell.

In example embodiment(s), a wireless device may receive a messageindicating a preconfigured uplink resource (PUR) configuration of acell. For example, the PUR configuration may indicate one or more firstPURs and/or a first downlink reference signal (DL RS) associated withthe one or more first PURs. For example, the wireless device maydetermine a trigger of a beam failure recovery request. For example, adetermination of the trigger may be based on a beam measurement quantityof the first DL RS being lower than a first threshold value and/or acell measurement quantity of the cell being higher than or equal to asecond threshold value. For example, the wireless device may transmit,based on the determination of the trigger, the beam failure recoveryrequest to the cell.

For example, the message may be a radio resource management (RRC)release message. For example, the one or more first PURs may be used fortransmission during an RRC non-connected state. For example, an RRCstate of the wireless device may transition to a Non-RRC_CONNECTED statecomprising an RRC inactive state and an RRC idle state. For example, thebeam measurement quantity may be a block success rate (e.g., 1-blockerror rate), a reference signal received power (RSRP), and/or areference signal received quality (RSRQ). For example, the secondthreshold value may be used for a cell reselection evaluation process.For example, the cell may be the one determined to camp on based on acell reselection evaluation process. For example, the PUR configurationmay indicate that an antenna port and/or spatial filter used to receivethe first DL RS are used for transmission via the one or more firstPURs. For example, the PUR configuration may indicate that the first DLRS is a radio link monitoring RS. For example, the beam failure recoveryrequest may comprise a PUR-RNTI of the wireless device. For example, thebeam failure recovery request may indicate a second DL RS as a candidatebeam. For example, the wireless device may initiate, based on thedetermination of the trigger, a random access procedure for transmittingthe beam failure recovery request. For example, the wireless device maytransmit, to the cell, a preamble associated with a second DL RS. Forexample, the wireless device may receive, from the cell, a random accessresponse to the preamble. For example, the wireless device may transmit,based on the random access response, a second transport block via theone or more PURs using the second DL RS. For example, the wirelessdevice may transmit, to the cell, a preamble associated with a second DLRS. For example, the wireless device may receive, from the cell and as afirst response to the preamble. For example, the first response maycomprise an uplink grant. For example, the wireless device may transmit,to the cell and based on the uplink grant, a second transport block. Forexample, the wireless device may receive, from the cell, a secondresponse to the second transport block. For example, the wireless devicemay transmit, based on the second response, a second transport block viathe one or more PURs using the second DL RS.

In example, embodiment(s), a wireless device may receive a messageindicating a preconfigured uplink resource (PUR) configuration of acell. For example, the PUR configuration may indicates one or more firstPURs and/or a first downlink reference signal (DL RS) associated withthe one or more first PURs. The wireless device may determine a triggerof a beam failure recovery request to the cell based on a beammeasurement quantity of the first DL RS and/or a determination to campon the cell. The wireless device may transmit, based on the trigger, thebeam failure recovery request to the cell. For example, the beammeasurement quantity is smaller than or equal to a threshold value. Forexample, the beam measurement quantity is at least one of a blocksuccess rate (e.g., 1-block error rate), a reference signal receivedpower (RSRP), and/or a reference signal received quality (RSRQ).

In example embodiment(s), a wireless device may receive one or more DLRSs of one or more cells. The one or more cells may comprise a firstcell where the wireless device camps on and a second cell. The wirelessdevice may determine to camp on a second cell based on cell measurementquantities of the one or more cells. The wireless device may abort abeam failure recovery procedure in response to the determining to campon the second cell. For example, the wireless device may trigger (orinitiate) the beam failure recovery procedure for the first cell basedon one or more beam measurement quantities of the first cell. Forexample, a cell measurement quantity of the first cell may be determinedbased at least one of the one or more beam measurement quantities. Forexample, the wireless device may receive a paging message from thesecond cell after the determining to camp on the second cell. Forexample, the wireless device may initiate a random access procedure onthe second cell after the determining to camp on the second cell.

In example embodiment(s), a wireless device may receive one or more DLRSs of one or more cells comprising a first cell where the wirelessdevice camps on and/or a second cell. For example, the wireless devicemay determine to camp on a second cell based on cell measurementquantities of the one or more cells. The wireless device may reset oneor more parameter values of a beam failure recovery procedure for thefirst cell in response to the determining to camp on the second cell.For example, the resetting one or more parameter values may comprisesetting one or more counter values to their initial values. For example,the resetting one or more parameter values may comprise stopping one ormore timers running for the beam failure recovery procedure.

What is claimed is:
 1. A method comprising: receiving, by a wirelessdevice, a release message indicating: a small data transmission (SDT)procedure, of a cell, for an inactive state of the wireless device; anda downlink reference signal (RS), of a plurality of downlink RSs of thecell, associated with the SDT procedure; and initiating, during the SDTprocedure, a beam failure detection and recovery procedure on the cellbased on: a measurement quantity of the downlink RS compared with afirst threshold; and a cell measurement quantity, of one or moredownlink RSs of the plurality downlink RSs, compared with a secondthreshold.
 2. The method of claim 1, wherein the inactive state of thewireless device comprises: a radio resource management (RRC) inactivestate; or an RRC idle state.
 3. The method of claim 1, wherein: themeasurement quantity of the downlink RS is based on a reference signalreceived power (RSRP) of the downlink RS; and the cell measurementquantity is based on an RSRP of each of the one or more downlink RSs. 4.The method of claim 1, wherein the release message indicates the firstthreshold.
 5. The method of claim 1, further comprising determining tocamp-on the cell based on the cell measurement quantity being comparedto the second threshold.
 6. The method of claim 1, wherein based on theinitiating the beam failure detection and recovery procedure, the methodfurther comprises: detecting a beam failure instance; and transmitting abeam failure recovery request based on the detecting the beam failureinstance.
 7. The method of claim 6, wherein: the beam failure recoveryrequest comprises a radio network temporary identifier (RNTI) of thewireless device; and the method further comprises receiving, from thecell and using the RNTI, a response to the beam failure recovery requestin the inactive state.
 8. The method of claim 7, further comprisinginitiating, based on the beam failure detection and recovery procedure,a random access procedure to transmit the beam failure recovery request.9. The method of claim 8, further comprising performing the randomaccess procedure comprising: transmitting, to the cell, a preambleassociated with a second downlink RS; and receiving, from the cell, arandom access response to the preamble.
 10. A wireless devicecomprising: one or more processors; and memory storing instructionsthat, when executed by the one or more processors, cause the wirelessdevice to: receive a release message indicating: a small datatransmission (SDT) procedure, of a cell, for an inactive state of thewireless device; and a downlink reference signal (RS), of a plurality ofdownlink RSs of the cell, associated with the SDT procedure; andinitiate, during the SDT procedure, a beam failure detection andrecovery procedure on the cell based on: a measurement quantity of thedownlink RS compared with a first threshold; and a cell measurementquantity, of one or more downlink RSs of the plurality downlink RSs,compared with a second threshold.
 11. The wireless device of claim 10,wherein the inactive state of the wireless device comprises: a radioresource management (RRC) inactive state; or an RRC idle state.
 12. Thewireless device of claim 10, wherein: the measurement quantity of thedownlink RS is based on a reference signal received power (RSRP) of thedownlink RS; and the cell measurement quantity is based on an RSRP ofeach of the one or more downlink RSs.
 13. The wireless device of claim10, wherein the release message indicates the first threshold.
 14. Thewireless device of claim 10, wherein the instructions further cause thewireless device to determine to camp-on the cell based on the cellmeasurement quantity being compared to the second threshold.
 15. Thewireless device of claim 10, wherein based on initiating the beamfailure detection and recovery procedure, the instructions further causethe wireless device to: detect a beam failure instance; and transmit abeam failure recovery request based on detecting the beam failureinstance.
 16. The wireless device of claim 15, wherein: the beam failurerecovery request comprises a radio network temporary identifier (RNTI)of the wireless device; and the instructions further cause the wirelessdevice to receive, from the cell and using the RNTI, a response to thebeam failure recovery request in the inactive state.
 17. The wirelessdevice of claim 16, wherein the instructions further cause the wirelessdevice to initiate, based on the beam failure detection and recoveryprocedure, a random access procedure to transmit the beam failurerecovery request.
 18. The wireless device of claim 17, wherein theinstructions further cause the wireless device to: transmit, to thecell, a preamble associated with a second downlink RS; and receive, fromthe cell, a random access response to the preamble.
 19. A non-transitorycomputer-readable medium storing instructions that, when executed by oneor more processors of a wireless device, cause the wireless device to:receive a release message indicating: a small data transmission (SDT)procedure, of a cell, for an inactive state of the wireless device; anda downlink reference signal (RS), of a plurality of downlink RSs of thecell, associated with the SDT procedure; and initiate, during the SDTprocedure, a beam failure detection and recovery procedure on the cellbased on: a measurement quantity of the downlink RS compared with afirst threshold; and a cell measurement quantity, of one or moredownlink RSs of the plurality downlink RSs, compared with a secondthreshold.
 20. The non-transitory computer-readable medium of claim 19,wherein the inactive state of the wireless device comprises: a radioresource management (RRC) inactive state; or an RRC idle state.